[ https://issues.apache.org/jira/browse/CASSANDRA-10767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141575#comment-15141575 ]
Paulo Motta commented on CASSANDRA-10767: ----------------------------------------- works on linux, will test windows version shortly. > 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 > Assignee: Yuki Morishita > Priority: Trivial > Fix For: 2.1.x, 2.2.x, 3.0.x, 3.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)