Well if thats how its supposed to work, it seems like I might as well load
each service up, and let it handle the connection directly...
>- "Seek3r" <[EMAIL PROTECTED]>:
>
>| I am new to qmail and tcpserver. I installed tcpserver and was
>| under the impression that it was a superserver like inetd, only
>| better. I conffigured to to manage qmail, qmail pop3, telnet, and
>| ftp. The thing I noticed when checking my processes was that
>| tcpserver had 2 processes for each of the services
>|
>| for example it had the following for telnet.
>| supervise /var/lock/telnetd tcpserver -v -c40 -x /etc/tcprules.d/telnetd.
>| tcpserver -v -c40 -x /etc/tcprules.d/telnetd.cdb -u0 -g0 0 telnet in.teln
>|
>| With inetd it only had inetd running, until the telnet port was hit,
>| then it would spawn the telnetd process.
>| I am curious if this is how its designed to work, or if I am doing
>| something wrong.
>
>Yes, this is how it is designed to work. No, you are probably not
>doing anything wrong. I believe inetd is designed under the
>assumption that having lots of little processes each listening to a
>single port is expensive compared to having just one process doing the
>job. tcpserver is designed under the opposite assumption. (Perhaps
>both assumptions are right, depending on your definition of
>"expensive", but I'll leave that question to others to ponder.)
>
>- Harald
