On Fri, Oct 01, 1999 at 05:26:38PM +0100, Fred Backman wrote:
> * 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?
How about
$ man inetd
On my FreeBSD system I find:
-R rate
Specify the maximum number of times a service can
be invoked in one minute; the default is 256.
However this can only be done "globally" for all services and you cannot
say "use 255 for smtp and 5 for all other services".
If you use ulimit (or whatever it's called in various shells) before you
start inetd you can set certain limits, but they apply for all services.
You cannot specify selective limits for individual services.
For the listen() backlog you probably have to consult the source code of
inetd for your system.
With tcpserver you can fine tune each parameter for each service
individually. For most services started from inetd this may not be needed,
for some it may be essential (smtp is a good candidate) and then tcpserver
is your friend.
\Maex
--
SpaceNet GmbH | http://www.Space.Net/ | Yeah, yo mama dresses
Research & Development | mailto:[EMAIL PROTECTED] | you funny and you need
Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0 | a mouse to delete files
D-80807 Muenchen | Fax: +49 (89) 32356-299 |
