[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: No solution to crond excessive logging to messages yet?



Am Fr, den 24.06.2005 schrieb Randall Shaw um 1:45:

> Regarding: 
> https://www.redhat.com/archives/fedora-list/2005-February/msg06858.html
> 
> After futzing with the log level for "auth" in syslog... I have come to the
> conclusion that it was poorly implemented in the crond daemon. I HAVE to set
> logging from 'auth' to 'auth.none', as no other log level squelches the
> messages. To me, that is poor implementation, that such useless messages are
> considered "emerg" level log events!
> 
> Has anyone come up with a better solution to this issue, and I didn't catch
> it in the list archives?

> -Randall Shaw

http://marc.theaimsgroup.com/?l=fedora-list&m=111747038807351&w=2

That was my suggestion. You do not drop the messages but put them in a
different log file, so you still have the ability to have a look at them
to recognize something unusual.

Alexander


-- 
Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773
legal statement: http://www.uni-x.org/legal.html
Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.27_FC2smp 
Serendipity 02:08:06 up 2 days, 10:22, load average: 0.52, 0.59, 0.50 

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]