Subject: Re: libc 12.148 bad for my syslogd
To: Christos Zoulas <firstname.lastname@example.org>
From: Hisashi T Fujinaka <email@example.com>
Date: 10/29/2006 22:19:09
On Mon, 30 Oct 2006, Christos Zoulas wrote:
> In article <firstname.lastname@example.org>,
> Geoff Wing <email@example.com> wrote:
>> Sometime after 2006.10.25.14.00.00 and before 2006.10.27.14.00.00
>> 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: (root) CMD FINISH (/usr/libexec/atrun)
>> Is syslogd working for everyone else? Christos?
> Just fixed it; it was a bug in fprintf().
I suppose this isn't going to bump the version number. This could come
back to haunt you.
Hisashi T Fujinaka - firstname.lastname@example.org
BSEE(6/86) + BSChem(3/95) + BAEnglish(8/95) + MSCS(8/03) + $2.50 = latte