The following reply was made to PR general/1787; it has been noted by GNATS.
From: Dean Gaudet <[EMAIL PROTECTED]> To: Matt Braithwaite <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: general/1787: accept loops on ENOTSOCK, filling up logfile Date: Wed, 11 Feb 1998 17:25:16 -0800 (PST) On 10 Feb 1998, Matt Braithwaite wrote: > i have found a number of tickets that sound a lot like this, but none that > are > exactly the same. there are perhaps 3-6 of the form ``accept/select in > http_main.c loops on some error, filling up the logfile.'' Linux is very guilty of this one. > in these tickets > you have been able to suggest specific fixes that go to the root of the > problem. > however, i think this loop could be more defensive, given that the case of > accept or select getting stuck on a particular error seems not entirely > uncommon. one possibility: count failed accept()s against the maximum > number > of connections permitted for a child process, so that in conditions like this > the logs won't fill up Interesting idea... 'cept I tend to run servers with MaxRequestsPerChild 100000. I think what I'll try to do is figure out what accept responses are expected and make the rest die immediately. In many of these cases the child is just useless at that point. Oh yeah your note about possibly missing SIGUSR1 -- it shouldn't matter because there is a generation check against the scoreboard to make sure the generation hasn't changed. Dean
