some questions

[Olaf Titz]

> inetd on most systems has a nasty habit of deciding that there are too
> many connections per second to a particular service and refusing to spawn
> any more instances of that service.  nnrpd under tcpserver would work

In fact that was the original _reason_ I started running nnrpd from
inetd. :-) That was on a LAN server (fast network but slow machine),
where several clients used the old Netscape which has the habit of
bombarding the server with connections, sending the load through the
roof (with a load average >50 on the 486 machine, the software
watchdog would reboot it). I patched inetd to resume service after a
minute (instead of 10 minutes), which is mostly unnoticeable to the
clients but stops the berzerk Mozillas.

Another "safety net" feature coming to my mind is init's "respawning
too fast". Sometimes I wish a similar thing in INN for failing channel
feeds.

Olaf