Well I'll be damned, that's what changed.

When I ran qmail from before, /usr/local/bin/multilog was in the path.  But
on reboot, I forgot to add /usr/local/bin/ to the default system path.  it
threw no error that it couldn't find multilog, it just sat there when I ran
supervise /service/qmail from the shell-prompt.  Now that I look, though,
multilog wasn't running before.

Good eye, I missed that.

Thanks so much! :)

Dustin

-----Original Message-----
From: Dave Sill [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 15, 1999 12:15 PM
To: [EMAIL PROTECTED]
Subject: RE: Defunct qmail-start after reboot


"Dustin Miller" <[EMAIL PROTECTED]> wrote:

>/var/qmail/rc:
>exec env - PATH="/var/qmail/bin:$PATH" \
>qmail-start ./Maildir/ multilog t /var/log/qmail
>
>/service/qmail/run:
>*symlinked to /var/qmail/rc*
>
>/etc/rc.d/rc.local:
>[snip]
>supervise /service/qmail &
>[snip]
>
>Here are the processes running once the whole shebang starts up (these same
>processes are running when you svc -d /service/qmail followed by an svc -u
>/service/qmail):
>  609 ?        S      0:00 tcpserver 0 pop-3 /var/qmail/bin/qmail-popup
>wfdevelo
> 4126 tty1     S      0:00 supervise /service/qmail
> 4127 tty1     S      0:00 qmail-send
> 4128 tty1     Z      0:00 [qmail-start <defunct>]
> 4129 tty1     S      0:00 qmail-lspawn ./Maildir/
> 4130 tty1     S      0:00 qmail-rspawn
> 4131 tty1     S      0:00 qmail-clean
> 6601 pts/0    S      0:00 grep qmail
>
>No logging taking place.

Try killing everything off and running:

    supervise /service/qmail &

interactively, as root. Look for an error message. I suspect
qmail-start can't find multilog.

-Dave

Reply via email to