[
https://issues.apache.org/jira/browse/CASSANDRA-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879021#action_12879021
]
Eric Evans commented on CASSANDRA-1004:
---------------------------------------
Jonathan Ellis:
bq. CASSANDRA-1181 (which may or may not amount to anything) would require
running Cassandra as root, fwiw
This _should_ be OK. My understanding of how jsvc drops privileges, is that it
occurs _after_ the JVM has been initialized, and after the apps init() has been
called (so that you can bind to ports < 1024 for example).
http://commons.apache.org/daemon/jsvc.html
Ted Zlatanov:
bq. the user name should be specified in one place, not hard-coded as
"cassandra". That way sites with real users named "cassandra" don't suffer and
the sysadmin can choose to use "root" if appropriate
The point here is integration with Debian systems, and installing a service
that should drop privileges at startup is something that results in the
creation of a system user on Debian systems. If you don't want to run Cassandra
as this user, you can always hack the init script (it is a conf file; changes
will be preserved across upgrades).
> Debian packaging should allow a specific user name and optionally create it
> as "cassandra" on install
> -----------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-1004
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1004
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Ted Zlatanov
> Attachments: cassandra-user.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
