Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (hermes.apache.org: domain of twh@iw.net designates
 216.16.0.22 as permitted sender)
Message-ID: <4287F21B.1030101@iw.net>
Date: Sun, 15 May 2005 20:06:35 -0500
From: Tom Hoefakker <twh@iw.net>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: [PATCH] PR 26467 child process can hang when piped logger goes
 away
References: <cc67648e050515062239ca48c@mail.gmail.com>
	 <42875AB2.7080105@iw.net> <cc67648e050515171643adcaf7@mail.gmail.com>
In-Reply-To: <cc67648e050515171643adcaf7@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

good point. I suspected there was a reason for the difference in 
behavior between this and mod_log_config.


Jeff Trawick wrote:
> On 5/15/05, Tom Hoefakker <twh@iw.net> 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?
>