Charles Cazabon said,
> You have two tcpserver instances, both trying to bind to the same interface(s)
> and port. At least one of those _has_ to be failing, and it should be showing
> up in your logs.
Steve said,
>>At which point, doing 'sh -x /var/qmail/supervise/qmail-pop3d/run'
>> gives me:
I use this to check for status on supervised processes.
bash-2.04# cd /var/qmail/supervise; svstat * */log
qmail-pop3d: up (pid 658) 178697 seconds
qmail-send: up (pid 9480) 178696 seconds
qmail-smtpd: up (pid 3846) 178697 seconds
qmail-pop3d/log: up (pid 11946) 178697 seconds
qmail-send/log: up (pid 7901) 178697 seconds
qmail-smtpd/log: up (pid 13335) 178697 seconds
When you supervise, and one of the "seconds" columns stays at 0 seconds, you
definitely have a
problem. After you reboot, or better yet, when your pop stops working, try that and
see what
happens.
Also, do not start pop3d from the command line if you are starting it in your boot
scripts, even if
pop3 is not working properly.
Hope that helped
Rick Up
