One thing that could help you a bit - if you are using a fairly
standard buildout.cfg from the unified installer, then it extends
base.cfg also in the zeocluster directory. You can copy the '[chown]'
section from base.cfg into buildout.cfg and then add/remove/modify
whatever chown/chmod operations you want, so that if and when you re-run
buildout, the necessary directories get the ownership and permissions
you're going for.
-Ken
On 10/6/11 4:07 PM, hydrostarr2 wrote:
bump. Thoughts? Would like to get this settled soon... getting close and
closer to "production release day." (Thx for any help.)
Am considering amending proposed approach, and only changing to
'plone:plone' for /usr/local/Plone/zeocluster/* (and NOT
/usr/local/Plone/zeocluster).
Further, if it hasn't yet been noted: user/group ownership change was needed
in at last one of our system installs in order for plone-based process to
update/write/whatever properly in one of the /usr/local/Plone/zeocluster/var
areas...fwiw.
hydrostarr2 wrote:
Any thoughts?
hydrostarr2 wrote:
Any general "best practice" recommendations for user/group ownership (in
Ubuntu 10/11) of /usr/local/Plone and all its dirs/files in its tree?
We've been running with inconsistent settings, and plan to standard on
all 'plone:plone' for /everything/ in /usr/local/Plone. eg:
Problems with this? Alternative suggestions (and if so, why?)?
--
View this message in context:
http://plone.293351.n2.nabble.com/User-group-ownership-all-plone-plone-tp6860860p6867398.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.
_______________________________________________
Setup mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-setup
_______________________________________________
Setup mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-setup
