Hi again, Peter,
> (Also, try just downing /service/bincimaps and have it stay down
> for a few minutes, could be that the kernel needs to time out
> the use of the port before tcpserver is allowed to use it again.)
Tried that. I left the service down for over an hour. Unfortunately, that
doesn't seem to make any difference.
> Ok, let's look elsewhere.. What do the Binc run files look like?
>
> /service/bincimap{,s}/run
Well, they were generated from the install:
****/service/bincimap/run
#!/bin/sh
# $Id: run.in,v 1.1.1.1 2003/08/18 18:06:05 andreaha Exp $
# daemontools supervise run-file for Binc IMAP Service.
exec 2>&1
exec tcpserver -c 100 -u 0 -g 0 \
-l $(hostname) -HDRP \
0 143 \
/var/qmail/bin/bincimap-up \
--logtype=multilog \
--conf=/var/qmail/control/bincimap.conf -- \
/bin/checkpassword \
/var/qmail/bin/bincimapd
****/service/bincimaps/run
#!/bin/sh
# $Id: run-ssl.in,v 1.1.1.1 2003/08/18 18:06:05 andreaha Exp $
# daemontools supervise run-file for Binc IMAP Service.
exec 2>&1
exec tcpserver -c 100 \
-l $(hostname) -HDRP \
0 993 \
/var/qmail/bin/bincimap-up \
--logtype=multilog \
--conf=/var/qmail/control/bincimap.conf --ssl -- \
/bin/checkpassword \
/var/qmail/bin/bincimapd
Cheers,
Dave
