[PATCH] (was Re: apbugs@hyperreal.org:Re: apache-api/4456: ErrorLog directive causes SIGPIPE when errors are present.)

[Aidan Cully <ai...@panix.com>]

This patch fixes the PR I submitted against the subject line.  What I
did was to split pconf in two:  one half would be for configuration, and
one half would hold the error log pool until configuration is completely
reloaded.  When we get a request to reload config, we drop the pconf
pool, reload config (which may or may not generate errors to be sent to
an external process, which previously would cause SIGPIPEs), destroy the
old logging pool, create a new log pool and open the error logs into that.
Except for the brief period of time in which we're spawning the new
logging processes, there's _always_ a logging process running.

I think this is a bit ugly, but at least it works..  Would someone with
permission please examine/commit this patch?

--aidan
-- 
Aidan Cully         "Chihuahuahuahuahua."
Panix Staff           --The Sugercubes
aidan@panix.com