At 20:40 3/01/99 -0800, Seek3r wrote:

>>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.)

>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...

Just a note..

Some services do not have a stand-alone mode (eg: qmail). Some do, but they
are horribly unreliable, or provide no connection/concurrency limiting in
stand-alone mode. This is what tcpserver is for. A lot of services on a
machine by default (eg: a default RH 5.2 box for example) are not even
worth running, and should be either removed or disabled. Some are useful,
and using tcpserver for these would be advisable.

tcpserver has a very small footprint, and it is useful for large programs
which normally will load themselves totally into memory and spawn a new
copy for each incoming connection. This reduces memory, but increases the
time to spawn a new connection. (As the code is not in memory and therefore
not immediately available. However, if this program is spawned a lot, you
can conversly end up with the program residing in disk cache.) You
basically have to suck it and see which option is preferrable to your needs.

BTW: You mentioned in an earlier post about using telnet and getting a
delay. tcpserver has a delay option (that is enabled by default) that makes
sure that there is no lagging data, before passing it to the application.
You will want to turn this option off (I think it's -D, but check the man
page to be sure), as this is what is causing the 'lag' you speak of. The
delay is very useful for a batch command style protocols like SMTP and POP,
but useless for an interactive style protocols like Telnet or SSH.

Stuart Young - [EMAIL PROTECTED] - [EMAIL PROTECTED]
(aka Cefiar) - http://amarok.glasswing.com.au/

[All opinions expressed in the above message are my]
[own and not necessarily the views of my employer..]

Reply via email to