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
> 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 on
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
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
--
-
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 m
