On Sat, Jan 24, 2009 at 3:06 PM, Michael Biebl <bi...@debian.org> wrote: > Rainer suspected atomic operations to be the root cause. This would mean a > problem in GCC at compile time. > rsyslog basically depends on zlib1g and libc6. I don't expect zlib1g to have > any > influence, so you might wanna check if libc6 has been updated on you system.
Just when I said I have had no problems... last night (not during cron job) rsyslog had crashed in my client (last lines of syslog attacted). So I can still reproduce this bug. Do you want to be sure and wait for another crash or do you want me to start be removing the $ActionQueue* directives from configuration? Regards, Juha
syslog
Description: Binary data