Bernhard Graf [EMAIL PROTECTED] wrote:
Gerrit Pape wrote
svscan should be started at boot time and never stopped until
shutdown. That ensures your services are always running with the
same (known and wanted) environment and limits.
But I don't want to bypass run levels.
Would you approve
Dave Sill [EMAIL PROTECTED] wrote:
Would you approve creating a 'down' file in the service directories and
running 'svc -u / svc -d' in init.d scripts on each service?
That's a nice idea, but it doesn't work. svscan started via inittab
isn't started until *after* the init.d scripts are
Charles Cazabon [EMAIL PROTECTED] wrote:
I could be mistaken, but I believe this behaviour depends on the order of the
various lines in inittab -- if you put svscan before the stuff called in the
standard runlevels, it should work.
Hmm, that could be it. If so, it's unfortunate that DJB's
On Mon, 18 Jun 2001, Charles Cazabon wrote:
I could be mistaken, but I believe this behaviour depends on the order
of the various lines in inittab -- if you put svscan before the stuff
called in the standard runlevels, it should work.
SysVinit, which I believe is quite common on Linux
On Sat, Jun 16, 2001 at 11:28:35PM +0900, YOON, Joo-Yung wrote:
Thanks for your help.
I checked the system, and found out that there were 2 places that initiate
svscan. The one is /etc/inittab, and the other is /etc/init.d/svscan.
Life with Qmail (installation document) misses the point
Gerrit Pape wrote
Better remove /etc/init.d/svscan and corresponding links and use the
inittab entry as recommended by the software author.
Why?
--
Bernhard Graf [EMAIL PROTECTED]
On Sun, Jun 17, 2001 at 03:18:37PM +0200, Bernhard Graf wrote:
Gerrit Pape wrote
Better remove /etc/init.d/svscan and corresponding links and use the
inittab entry as recommended by the software author.
Why?
svscan should be started at boot time and never stopped until shutdown.
That
Gerrit Pape wrote
On Sun, Jun 17, 2001 at 03:18:37PM +0200, Bernhard Graf wrote:
Gerrit Pape wrote
Better remove /etc/init.d/svscan and corresponding links and use the
inittab entry as recommended by the software author.
Why?
svscan should be started at boot time and never
On Sun, Jun 17, 2001 at 05:18:29PM +0200, Bernhard Graf wrote:
Gerrit Pape wrote
svscan should be started at boot time and never stopped until shutdown.
That ensures your services are always running with the same (known and wanted)
environment and limits.
But I don't want to bypass run
Thanks for your help.
I checked the system, and found out that there were 2 places that initiate
svscan. The one is /etc/inittab, and the other is /etc/init.d/svscan.
Life with Qmail (installation document) misses the point that
daemontool installs /etc/init.d/svscan and that it requests the
YOON, Joo-Yung [EMAIL PROTECTED] writes:
drwx--3 root root 4096 6¿ù 16 23:16 supervise
(There is another supervise inside the supervise directory.)
This is left from your previous wrong setup. There are supervise
directories on overy first level directory now. To remove
Dear Frank,
Thanks for your help.
I deleted all supervise directories, and it seems to work.
Warm regards,
On Sat, Jun 16, 2001 at 04:49:20PM +0200, Frank Tegtmeyer wrote:
YOON, Joo-Yung [EMAIL PROTECTED] writes:
drwx--3 root root 4096 6¿ù 16 23:16 supervise
12 matches
Mail list logo
