0000895: Crond logs uninmportant messages. - BusyBox Bug and Patch Tracking

Notes
(0001474) landley 06-29-06 10:07	What made you think a lower log level was less important? I just grepped through for the crondlog() calls and debug calls are 005, "ignoring" is 007, "process already running" is 011, inability to execute one of the commands is 024, significant clock skew detected is 111, inability to chdir to the crond database directory is 311... Seems like a pretty straightforward progression to me...

(0001476) mootinator 06-29-06 17:23	Myself and I suspect many other end users when they set a log level at runtime are expecting to set the level based on the standard levels set out in the definition for syslog where 0 is an emergency, and 7 is LOG_INFO. I can't even look at those values in the source and quickly determine where I want to set the log level, since those numbers are being logically & 0xf-ed before being compared to LogLevel (do you know what \311 & 0xf is off the top of your head?) It isn't a particularily useful implementation at the very least.

(0001479) landley 06-29-06 17:34	If you really, really want me to I can remove all logging from crond. Until then, this is working as designed.

Relationships