That is expected behavior. tcpserver spawns another instance of itself to
handle the communication for a specific connection request. (up to the
maximum specified by the -c option - default is 40).
On Wed, 2 Jun 1999, [iso-8859-1] "G�nthner, Ralf" wrote:
> No tcpserver entry in the rc script! And here's the ps output:
>
> ps auxww | grep qm
> qmaild 701 0.0 1.2 832 280 p0 S 15:49 0:00 tcpserver -v
> -x/etc/t
> cp.smtp.cdb -u33334 -g333 0 25 qmail-smtpd
> qmaild 796 0.0 1.2 832 296 p0 S 15:52 0:00 tcpserver -v
> -x/etc/t
> cp.smtp.cdb -u33334 -g333 0 25 qmail-smtpd
> qmaill 699 0.0 0.8 808 184 p0 S 15:49 0:00 accustamp
> qmaill 700 0.0 0.9 824 224 p0 S 15:49 0:00 cyclog
> -s5000000 -n5
> /var/log/qmail
> qmaill 704 0.0 1.2 824 284 p0 S 15:49 0:00 splogger
> qmail
> qmailq 707 0.0 0.9 816 216 p0 S 15:49 0:00 qmail-clean
> qmailr 706 0.0 1.0 820 228 p0 S 15:49 0:00 qmail-rspawn
> qmails 697 0.2 1.1 860 260 p0 S 15:49 0:00 qmail-send
> root 698 0.0 0.8 812 200 p0 S 15:49 0:00 supervise
> /var/lock/q
> mail-smtpd tcpserver -v -x/etc/tcp.smtp.cdb -u33334 -g333 0 25
> qmail-smtpd
> root 705 0.0 1.0 820 228 p0 S 15:49 0:00 qmail-lspawn
> ./Mailbo
> x
> root 802 0.0 1.4 896 340 p0 S 15:52 0:00 grep qm
>
> 701 and 796 are the son processes and 698 is the supervised process.
>
> After a restart I noticed that things were as they should be (there were
> only 698 and 701) as long as no new messages came in, but as soon as
> this happened process 796 came up....I monitored further and noticed
> that these additional tcpserver processes come and go. Maybe this is
> normal behavior and nobody noticed because when the system is idle,
> there's just the two initial processes??
>
> Cheers
> Ralf
>
>
---------------------------------
Timothy L. Mayo mailto:[EMAIL PROTECTED]
Senior Systems Administrator
localconnect(sm)
http://www.localconnect.net/
The National Business Network Inc. http://www.nb.net/
One Monroeville Center, Suite 850
Monroeville, PA 15146
(412) 810-8888 Phone
(412) 810-8886 Fax
