Why does Plone not come with a native /etc/init.d control script for
Linux/Ubuntu?  And how can I trust one that just gets pulled from a random
post like the ones below (which were found at top of "/etc/init.d Plone"
google search)?  Suggestions?

http://plone.org/documentation/kb/startup-script-for-debian/tutorial-all-pages
http://plone.org/documentation/kb/simple-etc-rc-d-init-d-script-for-zeocluster
http://plone.org/documentation/kb/startup-script-for-debian/the-script-it-self
(seems like latest/most-pertinent)

As server admins are response for coding our own
startup/shutdown/status/control script?  Been running zeocluster/bin/*.sh
scripts "by hand" for a while now. NOT running zopectl but rather
"restartclients.sh", "restartclusher.sh", "shutdowncluster.sh", etc.

An aside- this is just another thing that other webserver apps just "make
easy" and is a struggle in Plone.  :-/ There seems to be no authoritative
source for how to address a fundamental issue for install.  Also, the
'plonectl' script (from 4.1, below) looks nothing like the above scripts,
hence am hesitant to simply link it in to /etc/init.d and startup/shudown
control.



--
View this message in context: 
http://plone.293351.n2.nabble.com/etc-init-d-control-script-for-Linux-Ubuntu-tp6853834p6853834.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

Reply via email to