[
https://issues.apache.org/jira/browse/CASSANDRA-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396296#comment-13396296
]
Nick Bailey commented on CASSANDRA-4355:
----------------------------------------
I'm also wondering if there are any generally accepted practices regarding
giving the cassandra group itself write permissions to these directories/files.
>From the perspective of someone writing a monitoring application, I would like
>to be able to have our packaging create its own user and add that user to the
>cassandra group, and at that point have read/write access to configuration
>files/snapshots/other things.
> Better debian packaging permissions
> -----------------------------------
>
> Key: CASSANDRA-4355
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4355
> Project: Cassandra
> Issue Type: Bug
> Reporter: Nick Bailey
> Assignee: Nick Bailey
> Attachments: 0001-Better-permissions-in-deb-package.patch
>
>
> The debian package creates a cassandra user for the process to run as. It
> chowns /var/lib/cassandra and /var/log/cassandra, but it doesn't grant group
> level access to these files. It should do a 'chown cassandra:cassandra ...'
> so that users in the cassandra group can also access those files. Also we
> should chown /etc/cassandra and any other files/directories created.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
