Re: LWQ/svscan question
Dave can probably give a more detailed answer to this, but you don't symbolicly link the directories into /service until you're ready to run them. And even then, svscan won't start them until you do a svc -u (or -o) /service/servicename . Everything I've read about svscan says that once you create the symbolic link in /service that the new service will start within 5 seconds. I don't use svscan to run Qmail (mainly due to a newbie mess up when I initially installed Qmail and don't want to break what *IS* working fine for my needs) but I *DO* use svscan for djbdns and in every instance where I have installed djbdns and created the symbolic link in /service, dnscache has always started on it's own. FWIW Richard
LWQ/svscan question
I looked at the new version of Life with qmail for the first time today, so forgive me if this is a little late. I didn't see anything in the archive to suggest it had already been talked aobut. 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? That way you would have greater control over when and in what order the supervised services began during boot-up. ---Kris Kelley
Re: LWQ/svscan question
Charles Cazabon [EMAIL PROTECTED] wrote: Dave can probably give a more detailed answer to this, but you don't symbolicly link the directories into /service until you're ready to run them. That's not how LWQ's qmailctl works. The links in /service are permanent. And even then, svscan won't start them until you do a svc -u (or -o) /service/servicename . Sure it will, unless there's a down file. In short, stop worrying, I think :). Definitely. -Dave
Re: LWQ/svscan question
Dave Sill [EMAIL PROTECTED] wrote: And even then, svscan won't start them until you do a svc -u (or -o) /service/servicename . Sure it will, unless there's a down file. Of course, I received several corrections immediately after sending this. Mea culpa. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: LWQ/svscan question
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
