Jens Vagelpohl wrote:
Zope itself does not ship with an init.d script. So yes, this is most
likely a distribution/packaging issue that should be brought to the
packagers' attention.
FWIW, I've always found symlinking zopectl into init.d to work just fine...
Chris
--
Simplistix - Content
Hi Fernando,
In my debian distro, in order to have an init.d script, I added a new
file in /etc/init.d, let's name it zope.sh.
Whitin, code a daemon, like:
(beware i made it from my zope's insatnces over several machines and zeo
init script, so I haven't tested it (may contains typo).
Thanks for all the replies! I got quite a good picture of the situation.
Final solution was to symlink zopectl into init.d and run update-rc.d.
In the meanwhile, I've also come across two relevant links which might be
useful for someone else:
similar problem:
Hi,
As far as I can see and tried, the zope2.8 script only deals with instances
which are created in the default instance directory,
/var/lib/zope2.8/instance/.
I would prefer to keep a specific instance of zope in a different directory,
together with other related directories, e.g. files from
On 23 Nov 2005, at 23:59, Fernando Martins wrote:
Hi,
As far as I can see and tried, the zope2.8 script only deals with
instances
which are created in the default instance directory,
/var/lib/zope2.8/instance/.
I would prefer to keep a specific instance of zope in a different
