When I originally installed Zope 2.6.2 a startup script was created in /etc/init.d, although I don't recall how it got created. Does v2.7.3 create a new version of this file when running make install? If not, how is it created? -- John
John Poltorak wrote:
When I originally installed Zope 2.6.2 a startup script was created in /etc/init.d, although I don't recall how it got created. Does v2.7.3 create a new version of this file when running make install? If not, how is it created?
I suppose you are running zope on Debian The /etc/init.d scripts are not created while installing zope from source. If you install zope2.7 from the debian package (testing), you'll get new /etc/init.d scripts that will only take care of zope 2.7 instances HTH -- David Convent
On Wed, Nov 10, 2004 at 04:08:04PM +0100, David Convent wrote:
John Poltorak wrote:
When I originally installed Zope 2.6.2 a startup script was created in /etc/init.d, although I don't recall how it got created. Does v2.7.3 create a new version of this file when running make install? If not, how is it created?
I suppose you are running zope on Debian The /etc/init.d scripts are not created while installing zope from source. If you install zope2.7 from the debian package (testing), you'll get new /etc/init.d scripts that will only take care of zope 2.7 instances
I'm running on Linux Redhat 7.3. I don't remember installing a Zope package previously, although I may be mistaken. Doesn't the install process create the startup script?
HTH
-- David Convent
-- John
On Nov 10, 2004, at 19:08, John Poltorak wrote:
When I originally installed Zope 2.6.2 a startup script was created in /etc/init.d, although I don't recall how it got created. Does v2.7.3 create a new version of this file when running make install? If not, how is it created?
I'm running on Linux Redhat 7.3. I don't remember installing a Zope package previously, although I may be mistaken. Doesn't the install process create the startup script?
The source releases have their own startup scripts, and no, they will not touch system directories like /etc/init.d. Whatever it was that automatically installed something into /etc/init.d was not a source release from zope.org. The startup script (zopectl) that is created by Zope 2.7 can be linked into /etc/init.d and should work fine. jens
Am Mi, den 10.11.2004 schrieb John Poltorak um 19:08:
On Wed, Nov 10, 2004 at 04:08:04PM +0100, David Convent wrote:
John Poltorak wrote:
When I originally installed Zope 2.6.2 a startup script was created in /etc/init.d, although I don't recall how it got created. Does v2.7.3 create a new version of this file when running make install? If not, how is it created?
I suppose you are running zope on Debian The /etc/init.d scripts are not created while installing zope from source. If you install zope2.7 from the debian package (testing), you'll get new /etc/init.d scripts that will only take care of zope 2.7 instances
I'm running on Linux Redhat 7.3. I don't remember installing a Zope package previously, although I may be mistaken. Doesn't the install process create the startup script?
It does. All you have to do is to make a link from clients zopectl (and zeoctl if you have) to init.d directory, whereever this is hidden in redhat. /etc/... somewhere. And another links to the runlevels you want to start/stop. the *ctl scripts understand the arguments start and stop and so fit perfectly into Sys-V-style startup. Regards Tino
It does. All you have to do is to make a link from clients zopectl (and zeoctl if you have) to init.d directory, whereever this is hidden in redhat. /etc/... somewhere. And another links to the runlevels you want to start/stop.
the *ctl scripts understand the arguments start and stop and so fit perfectly into Sys-V-style startup.
Well, they fit mostly :) To make it perfect it should also contain the chkconfig declaration at the top to declare default start/stop orders. jens --------------- Jens Vagelpohl jens@zetwork.com Software Engineer +49-(0)441-36 18 14 38 Zetwork GmbH http://www.zetwork.com/
participants (4)
-
David Convent -
Jens Vagelpohl -
John Poltorak -
Tino Wildenhain