[jira] [Comment Edited] (CASSANDRA-10767) Checking version of Cassandra command creates `cassandra.logdir_IS_UNDEFINED/`

["Yuki Morishita (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-10767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15116527#comment-15116527 ] 

Yuki Morishita edited comment on CASSANDRA-10767 at 1/26/16 2:30 AM:
---------------------------------------------------------------------

{{cassandra -v}} invokes main method in {{GetVersion}} class, which trigger logback initialization through access to FBUtilities. We need to add "-Dcassandra.logdir=..." when using '-v' switch as well.

I will go through other scripts including windows one to make sure we are passing above. Scripts for tools should be using logback-tools.xml instead so I will check that as well.



was (Author: yukim):
{cassandra -v} invokes main method in {GetVersion} class, which trigger logback initialization through access to FBUtilities. We need to add "-Dcassandra.logdir=..." when using '-v' switch as well.

I will go through other scripts including windows one to make sure we are passing above. Scripts for tools should be using logback-tools.xml instead so I will check that as well.

> Checking version of Cassandra command creates `cassandra.logdir_IS_UNDEFINED/`
> ------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10767
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10767
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>         Environment: $ cassandra -v                                                                                                                    
> 2.1.2
> MacOSX 10.9.5
> $ brew info cassandra                                                                                                              [14:15:41]
> cassandra: stable 2.2.3 (bottled)
> Eventually consistent, distributed key-value store
> https://cassandra.apache.org
> /usr/local/Cellar/cassandra/2.1.2 (3975 files, 92M) *
>   Built from source
> From: https://github.com/Homebrew/homebrew/blob/master/Library/Formula/cassandra.rb
> ==> Caveats
> To have launchd start cassandra at login:
>   ln -sfv /usr/local/opt/cassandra/*.plist ~/Library/LaunchAgents
> Then to load cassandra now:
>   launchctl load ~/Library/LaunchAgents/homebrew.mxcl.cassandra.plist
>            Reporter: Jens Rantil
>            Priority: Minor
>             Fix For: 2.1.x, 2.2.x, 3.0.x
>
>
> When I execute `cassandra -v` on the terminal the directory `cassandra.logdir_IS_UNDEFINED` is created in my CWD:
> {noformat}
> $ tree cassandra.logdir_IS_UNDEFINED
> cassandra.logdir_IS_UNDEFINED
> └── system.log
> 0 directories, 1 file
> {noformat}
> Expected: That no log file nor directory is created when I'm simply checking the version of Cassandra. Feels a bit ridiculous.
> Additionals: Just double checking, is this a bundling issue that should be reported to Homebrew? Probably not, right?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)