Re: mulitlog not getting terminated when Red Hat reboots?

Brian Reichert <[email protected]> wrote:
> 
> Several people have brought up how svscan would affect me.  I should
> have mentioned that I do have a SysV-style init script explicitly
> that does do 'svc -d /service/foo/log', and there is the appropriate
> 'K23foo' symlink for my runlevel.
> 
> I can see that if I use my 'service foo stop' script from the command
> line, my foo multilog process is indeed stopped.
[...]
> Ergo, I should have met the conditions for a clean termination of
> multilog, and should have avoided this 'outage' condition.
> 
> Yet, it is happening.  One of my assumptions is being violated.

You assume `svc -d` stops a service from re-starting.  It does not.  It merely
tells the extant supervise process not to start the service.  You're *killing*
that supervise process.

Think: when supervise gets killed, svscan will start a new supervise process
for that service.  If the down file doesn't exist, the new supervise will
immediately start the service.

Charles
-- 
-----------------------------------------------------------------------
Charles Cazabon                              <[email protected]>
GPL'ed software available at:               http://pyropus.ca/software/
-----------------------------------------------------------------------