[
https://issues.apache.org/jira/browse/CASSANDRA-17773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571680#comment-17571680
]
Eric Evans commented on CASSANDRA-17773:
----------------------------------------
{quote}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…?
{quote}
Good catch [~mck], that is what happened here (I have a modified/unpatched
{{cassandra-env.sh}}). I think this still counts as buggy though:
{{cassandra-env.sh}} is marked as a conffile, as such it won't be overwritten
(by the patched version) at install time.
> 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: [email protected]
For additional commands, e-mail: [email protected]
