On Wed, Jul 04, 2001 at 01:41:40AM -0500, David Dahl wrote:
> I cannot get qmail to startup properly:
The examples you showed are from an installation that uses daemontools. Is
svscan running?
[...]
> shutdown and error:
> =============================================
> [root@mckenna bin]# /etc/init.d/qmailctl stop
> Stopping qmail...
> qmail-smtpd
> svc: warning: unable to control /service/qmail-smtpd: file does not exist
> qmail-send
> svc: warning: unable to control /service/qmail-send: file does not exist
Those directories aren't being supervised; probably svscan isn't running
> listing of /service:
> ==============================================
>
> [root@mckenna /service]# ls -lia
> total 16
> 32618 drwxr-xr-t 3 root qmail 4096 Jul 3 12:57 ./
> 32613 drwxr-xr-x 5 root qmail 4096 Jul 3 12:16 ../
> 32619 drwxr-xr-x 2 root qmail 4096 Jul 3 10:20 log/
> 32623 lrwxrwxrwx 1 root root 32 Jul 3 12:57
> qmail-send -> /var/qmail/supervise/qmail-send//
> 32624 lrwxrwxrwx 1 root root 33 Jul 3 12:57
> qmail-smtpd -> /var/qmail/supervise/qmail-smtpd//
> 32620 -rwxr-xr-x 1 root qmail 212 Jul 3 10:16 run*
Why is there a "log" directory and a "run" file in your /service? You have
your /service directory configured like it is a service itself; it's not.
the /service directory is used to tell svscan where to find services to
supervise. Also, the /service directory should be owned root.root, not
root.qmail .
You should only have symlinks to service directories in /service, like the
ones you have for qmail-send and qmail-smtpd . If svscan can't start those,
it writes messages to the console.
[...]
> do i even need xinietd with tcpserver?
No; tcpserver is a replacement for inetd-like tools.
> do i have permissions problems up in /service?
Apart from it being owned root.qmail, no.
Vince.
