Darren Tucker wrote:
> On Wed, Nov 16, 2005 at 01:21:19PM +0200, Rogan Dawes wrote:
>>To update any of the IP or TCP configuration options, system
>>administrators should use the program "tcpconfig". This prompts the
>>admin for a bunch of options, and then, once they have been confirmed,
>>it resets the ENTIRE IP stack, and applies the new settings. Clearly,
>>this is not something that should be done remotely!
>>However, the net result of this is that OpenSSH generates thousands of
>>error messages in the "accept" loop, filling up the (prehistoric) syslog
>>facility that has no concept of "previous message repeated 122342234 times"!
>>This continues even after the IP stack has completed reloading.
>>Would it be unreasonable to add some kind of loop counter that tracks
>>the number of consecutive accept errors, and if it reaches a certain
>>threshold, restarts the daemon from a suitable point?

> It would not be hard, but it seems like an awful hack. How do the
> native utilities behave under those circumstances?

They seem to handle it well enough, apparently.

The alternative is to run OpenSSH from inetd, if I can find out how to
make my changes persistent!

It may be cleaner in the long run.

Thanks for the speedy patch. I thought that the received_sighup would
have a role to play somehow.


openssh-unix-dev mailing list