Ben Beuchler <[EMAIL PROTECTED]> wrote:
>I'm launching tcpserver for my POP service from /var/qmail/rc, which looks
>like this:
>
>-------
>
>#!/bin/sh
>
># Using splogger to send the log through syslog.
># Using qmail-local to deliver messages to ~/Mailbox by default.
>
>exec env - PATH="/var/qmail/bin:$PATH" \
>qmail-start ./Maildir/ splogger qmail &
>
># Starts up qmail-smtpd
># Currently no logging. Will be fixed.
>
>/usr/local/bin/tcpserver -R -q -p -x /etc/smtprules/tcp.smtp.cdb -u79 -g1003 0 smtp \
> /var/qmail/bin/qmail-smtpd 2>&1 &
>
># Starts up POP3 server
>
>/usr/local/bin/tcpserver -q -R -u79 -g1003 0 pop3 \
> /var/qmail/bin/qmail-popup amazhan.bitstream.net \
> /var/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir &
>
>-------
>
>The odd thing is that I frequently end up with two tcpserver processes
>for POP3, both with identical command lines. As you can see, I am not
>running svscan or any of the daemontools...
Yeah: run svscan and some of the daemontools. :-) Homegrown startup
scripts are great for those who can grow their own. Others should use
proven scripts like those in LWQ.
You could end up with two POP3 tcpservers if your re-ran your script
without killing the old one off.
-Dave
