[
https://issues.apache.org/jira/browse/CASSANDRA-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105042#comment-13105042
]
Shyamal Prasad commented on CASSANDRA-3198:
-------------------------------------------
BTW, I tested the snippet in Eric's comment with the additional pre-0.6.4-2
check (my patch) pretty extensively: install, upgrade to package with new
version, remove and reinstall etc. It certainly looks right, and I am sure it
works because I tried it, several ways. I did not test the upgrade from 0.6.4-2
since I did not completely understand why it was important, but I left it in
once I traced it down to CASSANDRA-1004. As I suspected there's people out
there that know better :-)
(BTW, in testing I found one minor irritation that
/var/log/cassandra/output.log gets created owned by root after installation. I
suspect this is because it is created before jsvc switches the user to after
allowing privileged operations to complete...once I'm sure the problem is real
I'll file it separately....but it was a good test case for the patch!)
> debian packaging installation problem when installing for the first time
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-3198
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3198
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
> Affects Versions: 0.8.5
> Reporter: Jérémy Sevellec
> Assignee: Jérémy Sevellec
> Fix For: 0.8.6
>
> Attachments: debian-postinst-fixperms.patch, trunk-3198-v1.patch
>
>
> when installing cassandra through the debian packaging for the first time,
> there is permission problem when starting Cassandra.
> Normally, the postinst script change owner of /var/log/cassandra and
> /var/lib/cassandra from root to cassandra user.
> there is a problem with the test which verify if threre is a need to change
> the owner of these directory or not.
> On a new install, the $2 parameter is not set and the the test is false and
> the owner is not changed.
> (simply, i think replace "&&" with "||" might work)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
