"Timothy L. Mayo" <[EMAIL PROTECTED]> wrote:
>
>I stand by my original statement (or hang).
>
>On a moderately busy (50 messages/minute for ~16 hours per day), there is
>a tcpserver process spawned for every incoming connection attempt. I
>usually have 35-40 of these present on the system in addition to the one
>started by supervise. Each of these authenticates the IP address the
>connection is coming from and then spawns qmail-smtpd. The tcpserver
>process does NOT exit until the qmail-smtpd is finished.
>
>This is on Dec UNIX.
>
>Again, this is expected behavior. It may depend on the OS though.
OK, I'm talking now about my own Dec UNIX box, a list server. It
doesn't do as much incoming traffic as yours, so typically I have no
active qmail-smtpd processes:
root@sws1# ps -ef|grep smtpd
root 509 507 0.0 Apr 15 ?? 0:00.05 supervise
/var/supervise/tcpserver-qmail tcpserver -t5 -u 49491 -g 31314 0 smtp tcpcontrol
/etc/tcp.smtp.cdb /var/qmail/bin/qmail-smtpd-wrapper
qmaild 517 509 0.0 Apr 15 ?? 6:47.20 tcpserver -t5 -u 49491 -g
31314 0 smtp tcpcontrol /etc/tcp.smtp.cdb /var/qmail/bin/qmail-smtpd-wrapper
If I connect to port 25, a qmail-smtpd shows up right away:
root 509 507 0.0 Apr 15 ?? 0:00.05 supervise
/var/supervise/tcpserver-qmail tcpserver -t5 -u 49491 -g 31314 0 smtp tcpcontrol
/etc/tcp.smtp.cdb /var/qmail/bin/qmail-smtpd-wrapper
qmaild 517 509 0.0 Apr 15 ?? 6:47.22 tcpserver -t5 -u 49491 -g
31314 0 smtp tcpcontrol /etc/tcp.smtp.cdb /var/qmail/bin/qmail-smtpd-wrapper
qmaild 2288 517 0.4 12:05:46 ?? 0:00.11 /var/qmail/bin/qmail-smtpd
Connect again, get another:
root 509 507 0.0 Apr 15 ?? 0:00.05 supervise
/var/supervise/tcpserver-qmail tcpserver -t5 -u 49491 -g 31314 0 smtp tcpcontrol
/etc/tcp.smtp.cdb /var/qmail/bin/qmail-smtpd-wrapper
qmaild 517 509 0.0 Apr 15 ?? 6:47.23 tcpserver -t5 -u 49491 -g
31314 0 smtp tcpcontrol /etc/tcp.smtp.cdb /var/qmail/bin/qmail-smtpd-wrapper
qmaild 2288 517 0.0 12:05:46 ?? 0:00.11 /var/qmail/bin/qmail-smtpd
qmaild 18284 517 0.4 12:06:53 ?? 0:00.08 /var/qmail/bin/qmail-smtpd
It's possible, I suppose, that differences in our
supervise/tcpserver/qmail-smtpd configurations are causing your
qmail-smtpd's to show up in ps as tcpserver's. One thing I do that not
everyone does is to wrap qmail-smtpd in a shell script that does a
ulimit.
However, even if qmail-smtpd's display as tcpserver's, there should
only be two tcpserver's if there is an active incoming SMTP
connection. That can be determined by doing "netstat -a|grep smtp",
e.g.:
root@sws1# netstat -a|grep smtp
tcp 0 0 sws1.ctd.ornl.go.1651 xxx.40.210.221.smtp ESTABLISHED
tcp 0 0 sws1.ctd.ornl.go.smtp malachite.esd.or.2739 ESTABLISHED
The first line of output represents an outgoing SMTP connection (the
local port is 1651). The second line is an incoming connection (smtp
port).
So if you've got two tcpserver's for smtpd, but no incoming SMTP
connections, something's not right.
-Dave
