Subject: Re: libc 12.148 bad for my syslogd
To: None <>
From: Christos Zoulas <>
List: current-users
Date: 10/30/2006 05:14:28
In article <>,
Geoff Wing  <> wrote:
>Sometime after 2006. and before 2006.
>a version of libc broke my syslog functionality.  Now most stuff
>goes to /var/log/messages (where it should be ignored due to FOO.none
>directives) and not other files.  e.g. cron log entries in /var/log/messages:
>Oct 30 14:40:00 g <Oct 30 14:40:00 [: (root) CMD FINISH (/usr/libexec/atrun)
>instead of normal cron log file:
>Oct 30 12:00:00 g cron[10790]: (root) CMD FINISH (/usr/libexec/atrun) 
>Is syslogd working for everyone else?  Christos?

Just fixed it; it was a bug in fprintf().