Hello,

I hope I'm not making late and useless interference, but I have also
Slackware Linux (4.0.0 kernel 2.2.6) running and installed qmail 1.03,
ucspi-tcp 0.84 and daemontools 0.61. 

The first thing I want to say is that if you (Mark) also intend to use
daemontools 0.61 the startup/shutdown script in LWQ is no longer valid.

I'm using the following approach:

1. The rc.M file in /etc/rc.d looks as follows (just the part concerning
qmail):

# Commented out the sendmail lines

# Start the sendmail daemon:
# if [ -x /usr/sbin/sendmail ]; then
#  echo "Starting sendmail daemon (/usr/sbin/sendmail -bd -q15m)..."
#  /usr/sbin/sendmail -bd -q15m
# fi

#
# Start the qmail system
#
if [ -x /etc/rc.d/rc.qmail ]; then
 echo "Starting qmail ..."
 . /etc/rc.d/rc.qmail
fi

2. rc.qmail is a link to /var/qmail/rc

3. /var/qmail/rc looks as follows

#!/bin/sh
cd /var/qmail/services
/usr/bin/env - PATH="/usr/local/bin:/var/qmail/bin" ./svscan &

4. Note that I've created a directory /var/qmail/services. There I have a
copy of svscan. I had to cd to /var/qmail/services and start svscan there
because it didn't work otherwise.

5. /var/qmail/services contains two subdirectories: startup and smtpd both
containing a script run and a subdirectory log which again contains a
script run (for details please look at the documentation of daemontools
0.61 at ftp://koobera.math.uic.edu/www/daemontols.html - I got on this
site from www.qmail.org)

6. As an example I give here the run scripts in:

/var/qmail/services/startup 



#!/bin/sh

# Using qmail-local to deliver messages to ~/Mailbox by default.

exec /usr/bin/env - PATH="/var/qmail/bin" \
qmail-start ./Mailbox



and /var/qmail/services/startup/log



#!/bin/sh

# Using multilog to log messages from qmail-send in /var/qmail/log/qmail

exec /usr/bin/env - PATH="/usr/local/bin" \
multilog t /var/qmail/log/qmail '-*'


7. Note that /var/qmail/services/startup and /var/qmail/services/smtpd
have the sticky bit set.

NOTE: I'm not sure that this is a really good way to setup qmail but till
now it worked and I rebooted the system two or three times to see if
everything works after and it does.

Best regards,

Serban

Reply via email to