Jeff Trawick wrote:
On 5/15/05, Tom Hoefakker <[EMAIL PROTECTED]> wrote:
Perhaps while we're dealing with piped log process/pipe management perhaps we can take care of this one at the same time:
http://issues.apache.org/bugzilla/show_bug.cgi?id=34537
My own rationalization for current behavior (admittedly weak): If the access log piped logger keeps crashing, at least there is an error log for reporting the problem, so it isn't the worst thing in the world to keep trying to start the darn thing over and over and over (fork-a-matic) since we report what we're trying to do. Is it okay to try over and over to restart an error log piped logger if there is nowhere to report the issue?
