You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "mck (JIRA)" <ji...@apache.org> on 2019/06/04 02:46:00 UTC
[jira] [Commented] (CASSANDRA-14305) Use $CASSANDRA_CONF not
$CASSANDRA_HOME/conf in cassandra-env.sh
[ https://issues.apache.org/jira/browse/CASSANDRA-14305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855246#comment-16855246 ]
mck commented on CASSANDRA-14305:
---------------------------------
Thanks for spotting and raising that [~samt]. I am looking into it.
> Use $CASSANDRA_CONF not $CASSANDRA_HOME/conf in cassandra-env.sh
> -----------------------------------------------------------------
>
> Key: CASSANDRA-14305
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14305
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config
> Reporter: Angelo Polo
> Assignee: Angelo Polo
> Priority: Low
> Fix For: 3.11.5, 4.0
>
> Attachments: conf_cassandra-env.sh.patch
>
>
> CASSANDRA_CONF should be used uniformly in conf/cassandra-env.sh to reference the configuration path. Currently, jaas users will have to modify the default path provided for cassandra-jaas.config if their $CASSANDRA_CONF differs from $CASSANDRA_HOME/conf.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org