"Dan Poirier" <[email protected]> writes: > httpd issues the message > > "server reached MaxClients setting, consider raising the > MaxClients setting" > > as soon as the number of spare threads drops below MinSpareThreads. In > a pathological case where MinSpareThreads is high, the number of threads > actually in use might be nowhere near MaxClients. > > Here's a possible solution. It checks whether we're really at > MaxClients, or just below MinSpareThreads, and issues a more accurate > message. The new message will only be issued once. If we do hit > MaxClients for real, the original message will still be issued.
Thanks to Greg Ames who pointed out that I forgot to set the reported flag after issuing the new message. Any other comments? -- Dan Poirier <[email protected]>
