You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2010/08/18 22:59:22 UTC
[jira] Commented: (CASSANDRA-1407) debian init script could be more
consistent w/ bin/cassandra
[ https://issues.apache.org/jira/browse/CASSANDRA-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900033#action_12900033 ]
Brandon Williams commented on CASSANDRA-1407:
---------------------------------------------
+1
> debian init script could be more consistent w/ bin/cassandra
> ------------------------------------------------------------
>
> Key: CASSANDRA-1407
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1407
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
> Affects Versions: 0.7 beta 1
> Reporter: Eric Evans
> Assignee: Eric Evans
> Attachments: v2-0001-CASSANDRA-1407-refactor-assigment-of-JAVA_HOME-in-init.txt, v2-0002-CASSANDRA-1407-use-conf-cassandra-env.sh-in-place-of-d.txt
>
>
> With the introduction of conf/cassandra-env.sh it should be possible to eliminate the separately maintained /etc/default/cassandra. The init script should also use a JAVA_HOME derived from the java binary in PATH (if it exists), both because this is how things work in Debian (_the_ Java is the one chosen by alternatives), and because this is how bin/cassandra works as well.
> Patches to follow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.