Bug 681 - Crond always register all events into syslog as an error
Summary: Crond always register all events into syslog as an error
Status: RESOLVED FIXED
Alias: None
Product: Busybox
Classification: Unclassified
Component: Standard Compliance (show other bugs)
Version: 1.13.x
Hardware: PC Linux
: P5 minor
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-25 17:26 UTC by Oriol
Modified: 2009-12-15 01:20 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:


Attachments
Fix (4.41 KB, patch)
2009-12-13 16:42 UTC, Denys Vlasenko
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Oriol 2009-10-25 17:26:49 UTC
When crond is started with the -S (syslog) param, all the events are registered in syslogd as "error". Maybe it should be less alarming registering them as "notice" except when the cron'd task has ended with a !=0 return value.

At this point, I'm using Busybox 1.13.4.

Thanks in advance!
Comment 1 Denys Vlasenko 2009-12-13 05:01:43 UTC
glibc bug:

https://bugzilla.redhat.com/show_bug.cgi?id=547000
Comment 2 Denys Vlasenko 2009-12-13 05:02:49 UTC
Please disregard last comment
Comment 3 Denys Vlasenko 2009-12-13 16:42:13 UTC
Created attachment 837 [details]
Fix

Please try attached patch
Comment 4 Denys Vlasenko 2009-12-15 01:20:34 UTC
Fixed in git, will be in 1.16.x