Re: Trouble with Loglevel and log generation

[prev] [thread] [next] [Date index for 2004/11/26]

From: Rici Lake
Subject: Re: Trouble with Loglevel and log generation
Date: 19:54 on 26 Nov 2004
On 26-Nov-04, at 11:14 AM, Stas Bekman wrote:

> mathieu.millet@xxxx.xx wrote:
> [...]
>> More precisely, if I set (for example) the LogLevel to "error", I 
>> only get
>> error and more critical logs AND also "notice" logs (but not warn 
>> logs).
>
> I can reproduce that problem. I'll keep you posted when I get a chance 
> to debug it.
>
>> If I set to anything more critical than notice, I still get notice 
>> logs.
>> For more details :
>> Some versions : Red Hat Entreprise Linux 3
>> Apache 2.0.46 (rpm : 2.0.46-44.ent)
>> Mod_perl 1.99_09 (rpm : 1.99_09-10.ent)
>
> Unrelated, you are using very old versions of component. Please 
> consider upgrading to mp 1.99_17 and Apache 2.0.52. (though I can 
> still see the problem with the latest ones)

This behaviour, although not well documented, is by design. Notice logs 
are (apparently) supposed to be used for startup messages and are never 
masked *unless* you set the error log to use syslog.

You can see this behaviour clearly in httpd/server/log.c, line 375

R.


        -- 
        Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html

Trouble with Loglevel and log generation
mathieu.millet 14:41 on 26 Nov 2004

Re: Trouble with Loglevel and log generation
Stas Bekman 16:14 on 26 Nov 2004

Re: Trouble with Loglevel and log generation
Rici Lake 19:54 on 26 Nov 2004

Re: Trouble with Loglevel and log generation
Stas Bekman 20:04 on 26 Nov 2004

Generated at 11:26 on 21 Dec 2004 by mariachi v0.52