Message-ID: <34CB9896.85A6E75B@topsail.org>
Date: Sun, 25 Jan 1998 14:55:02 -0500
From: Chuck Murcko <chuck@topsail.org>
Organization: The Topsail Group[
MIME-Version: 1.0
To: new-httpd@apache.org
Subject: Re: [PATCH] Re: general/1555: excessive error log messages ...
References: <Pine.LNX.3.95dg3.980125043626.16366C-100000@twinlark.arctic.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

Dean Gaudet wrote:
> 
> Then how about Roy answers all the PRs related to them.  ;)
> 
> Seriously, we should change the message at the very least.  Something so
> that we don't have to explain to folks that they're "normal".  If they're
> not really "normal" then something is subtly broken with the server... but
> I don't really have any reason to believe that.
> 
> When I surf I hit ESC a bunch, and I know each time I do that I'm probably
> putting a few "send body lost connection" into the logs.  I really don't
> see what use they are to the admin given that this is probably a really
> common occurance.
> 
> Does anyone do anything useful with these warnings?
> 
> Dean
> 
> On Sun, 25 Jan 1998, Roy T. Fielding wrote:
> 
> > > > Synopsis: excessive  error log messages ... "send body lost connection to:
> > >xxx.xxx.xxx.xxx : Broken pipe"
> > >
> > >How about logging these errors at 'notice' level instead of 'warn'?
> >
> > -1.  They are warnings.  Besides, we treat the 'notice' level as
> > being more important than 'warn', resulting in a message regardless
> > of the loglevel.  APLOG_NOTICE is only used for things that we
> > absolutely want to appear in the log.
> >
I agree with Roy. The reasons for his -1 are the reasons we added
'warning' level logging to Apache in the first place. They replaced
timeout errors, if I remember correctly.
-- 
chuck
Chuck Murcko            The Topsail Group             West Chester PA
USA
chuck@topsail.org