sysklogd use strcpy with overlapping region when handling line continuation (backslash at the end of the line). The problem exposed only with SSE3 enabled glibc. More details on debian bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586156
Created attachment 247264 [details, diff] fix from debian bug thread
This fixed the problem of syslogd mangling up the config file and spewing nonsense for me.
should be fixed in sysklogd-1.5-r1
When is 1.5 going to be stable? The buggy 1.4.2_pre* is still the only stable version. If 1.5 is not ready for the prime-time yet then please apply the patch and bump -rX on 1.4.2.
I've just stumbled upon this one. My syslog.conf has *.=debug;\ auth,authpriv.none;\ news.none;mail.none -/var/log/debug and it results in cfline(*.=debug;auth,authpriv.none;newsil.ne;mail.none -/var/log/debug) symbolic name: debug ==> 7 symbolic name: none ==> 16 symbolic name: auth ==> 32 symbolic name: authpriv ==> 80 symbolic name: neCalled logerr, msg: unknown priority name "ne" logmsg: syslog.err<43>, flags 4, from localhost, msg syslogd: unknown priority name "ne" I'm using 1.4.2_pre20061230-r2 which is marked as stable. Is this stable version supposed to behave like that?
(In reply to comment #5) > I'm using 1.4.2_pre20061230-r2 which is marked as stable. > > Is this stable version supposed to behave like that? You should unkeyword sysklogd-1.5-r1, and see if it works fine with stable. If it does, open a stabilization request bug. (or, switch to something that's actively maintained - even Debian switched to rsyslog)
rsyslog is already in the tree. we dont force loggers.
