[syslog-ng] [Bug 142] --worker-threads=0 support

[bugzilla at bugzilla.balabit.com]

https://bugzilla.balabit.com/show_bug.cgi?id=142





--- Comment #8 from Balazs Scheidler <bazsi at balabit.hu>  2011-11-12 20:12:35 ---
ok, reopen is valid then. if syslog-ng stalls, then the main thread is doing something on the blocked filesystem, which blocks that too.

can you run syslog-ng under strace in a mode that displays threads as well and see why the main thread is getting stalled?

please make sure that the strace is complete, syslog-ng goes into the background and stracing the startup doesn't really help.

something like:

strace -ttT -o syslog-ng.log -s 256 -f /sbin/syslog-ng -Fe

Then produce the problem. The interesting portion of the strace is what the main thread is doing once the D state hits. It is either blocking on a
mutex/condvar
or it is doing something on the broken filesystem. I've quickly browsed the related code, and no obvious thing stood out.


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.