Bug 681

Summary:	Crond always register all events into syslog as an error
Product:	Busybox	Reporter:	Oriol <opalenzuela>
Component:	Standard Compliance	Assignee:	unassigned
Status:	RESOLVED FIXED
Severity:	minor	CC:	busybox-cvs
Priority:	P5
Version:	1.13.x
Target Milestone:	---
Hardware:	PC
OS:	Linux
Host:		Target:
Build:
Attachments:	Fix

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