I'm reading the web page about ucspi-tcp and see the last three lines which
say:

* inetd is unreliable under high loads. It cuts off service for 10 minutes
if it receives ``too many'' connections in 1 minute.
* inetd does not provide effective resource management. It will happily use
up all your memory if you are running a popular service.
* inetd has trouble with sudden bursts of activity. Its listen() backlog is
typically only 5 or 10 and cannot be raised.

Where can I find further documentation and proof or witnesses of this
actually being true?

TIA
Fred

Reply via email to