cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8142) prevent the command "cassandra start" from starting a cluster
Date Mon, 16 Nov 2015 09:54:11 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006429#comment-15006429
] 

Sylvain Lebresne commented on CASSANDRA-8142:
---------------------------------------------

bq.  so could also be applied 2.1, 2.2, 3.0

I disagree. This could very much break people on upgrade. Even if the work-around is simple,
user expect minor updates to be surprise-free.

Also I do think silently accepting random arguments (and doing nothing with them) is not great
and we should fix it if possible. Especially since that's definitively not the original intent
of the startup script. So let's please fix this on that ticket and not ignore the problem,
even if we do go further than just this.

> prevent the command "cassandra start" from starting a cluster
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-8142
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8142
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Packaging
>            Reporter: Steven Lowenthal
>            Assignee: Robert Stupp
>
> Students often type 
> "sudo service cassandra start" wrong, and type "sudo cassandra start".
> Running a package installation as root messes up their environments.
> since "start" is not a valid option on the "cassandra" command, we should block cassandra
from starting.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message