[
https://issues.apache.org/jira/browse/CASSANDRA-17773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17683303#comment-17683303
]
Claude Warren commented on CASSANDRA-17773:
-------------------------------------------
No, the intention here was for the nodetool to be an example of how to use the
script and the changes it brings. My plan is to update all relevant script to
use the new file.
Rather than do all the tools first I wanted to provide the new file and an
example to get feedback before proceeding. It would also be nice to get
feedback regarding how to proceed. I see options being:
# Do all the changes in one go.
# accept this pull request and do other changes in some sort of grouping (not
sure what that grouping would be but...)
# accept this pull request and do the other changes as individual pull
requests.
There is probably a middle ground 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
