--On Wednesday, May 15, 2002 4:29 PM -0400 Lawrence Greenfield
<[EMAIL PROTECTED]> wrote:
> Date: Wed, 15 May 2002 16:02:42 -0300
> From: Henrique de Moraes Holschuh <[EMAIL PROTECTED]>
> [...]
> The point is, if that indeed happens, log or no log, master loses
> track of the number of children that can service requests. That would
> be a bug, and the patch supposedly fixes this bug. It really doesn't
> matter (for accepting or not the patch) why the child died.
>
> Yes, I understand that. However, if the master (in real life
> situations) is actually losing track of the number of available
> service processes without one of those service processes crashing
> (either by the sysadmin or otherwise) then there's some other problem
> in the child accounting.
>
> I'd like to know if there is before doing something that may mask the
> problem completely.
>
> Larry
Would it be sufficient if the patch were altered slightly to send a
LOG_DEBUG message to syslog every time the master decremented one of the
worker counters, specifying what it did? Right now, it seems like the
indicator of the problem is a service unavailability. If key step in the
process that we're covering is the report of the dead child to the master,
and you'd be just as happy with a log message as a blatantly obvious
failure, well heck, let's do it! I'm happy to send you any bit of logging
information you want, just so long as my servers stay available! :)
Michael Bacon
OIT Systems Administration
