[ https://issues.apache.org/jira/browse/CASSANDRA-17773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571327#comment-17571327 ]
Michael Semb Wever commented on CASSANDRA-17773: ------------------------------------------------ {{cassandra-env.sh}} is sourced first, and if {{CASSANDRA_LOG_DIR}} is unset then sets it to {{/var/log/cassandra}} (not to {{$CASSANDRA_HOME/logs}} as the description states) See https://github.com/apache/cassandra/blob/trunk/debian/patches/cassandra_logdir_fix.diff#L19 Are we sure that this isn't a case of an old {{cassandra-env.sh}} file being kept in a newer installation…? Some testing is required I think… > Incorrect cassandra.logdir on Debian systems > -------------------------------------------- > > Key: CASSANDRA-17773 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17773 > Project: Cassandra > Issue Type: Bug > Components: Packaging > Reporter: Eric Evans > Priority: Normal > Labels: lhf > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1-rc > > > The Debian packaging patches bin/cassandra to use /var/log/cassandra for > logs, it does so conditionally however, only if CASSANDRA_LOG_DIR is unset. > This occurs _after_ cassandra-env.sh is sourced though, which also sets > CASSANDRA_LOG_DIR if unset (to $CASSANDRA_HOME/logs). The result is that > -Dcassandra.lodir is set to /usr/share/cassandra/logs on Debian systems. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org