[
https://issues.apache.org/jira/browse/CASSANDRA-17773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17683159#comment-17683159
]
Stefan Miklosovic commented on CASSANDRA-17773:
-----------------------------------------------
hi [~claude], thank you for the work on that patch after my review. I was
thinking about this lately, I apologize if this is somehow implicitly known
already .... The patch is introducing a new file and it is used in nodetool. My
question is - is nodetool the only script we need to do this for? There is a
lot of scripts which are calling some particular class like tools etc ... is
this new file meant to be sourced in every script or only some subset?
Also, there is this "habit" for people who are coding 3rd party tools which are
using Cassandra binaries / etc to use the skeleton of a script which just
differs in a class to be executed. Does this mean that one we merge this,
people suddenly need to take into account this new file and source it as well?
> 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
> Assignee: Claude Warren
> Priority: Normal
> Labels: lhf
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 4.x
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> 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]