I wrote:
> > Since the new LWQ sets up svscan to run independently of the qmail
control
> > script, would it not be a wise idea to include a "down" file in each
> > supervise directory, so that qmail and any other services would not
start
> > up when svscan is run?
Dave Sill replied:
> That was my original goal, but I soon discovered that the qmail init
> script was being run before svscan was started, so qmail wasn't
> starting when the system was rebooted. I opted to remove the "down"
> files and let svscan start them ASAP, which is safe since the init
> scripts have alread been run by that point.
I think I'd prefer to have svscan running before any of the relevant init
scripts were executed, because I plan on "supervise"-ing other programs
besides qmail. I like the idea of having them all in one place, overseen
by one svscan process (my current set-up calls svscan three times), but
would like more control over what order the services are started. So what
I'll probably do is call svscan from its own start-up script that runs
before the scripts of qmail and the other programs, and sprinkle "down"
files where appropriate. It doesn't look like it, but would I be at the
risk of breaking anything else in the LWQ scheme of things if I do it this
way?
Charles Cazabon wrote:
> Mea culpa; I claim "brain fade".
Been there, done that, can't remember what happened.
---Kris Kelley
