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

[bugzilla at bugzilla.balabit.com]

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


Balazs Scheidler <bazsi at balabit.hu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bazsi at balabit.hu




--- Comment #4 from Balazs Scheidler <bazsi at balabit.hu>  2011-10-31 05:46:33 ---
hmm, I'm not sure why that happens, either the D state in the kernel (uninterruptible sleep)
applies to the whole process, not just to a single thread.

or, a lock is being held accross the write syscall, which causes a deadlock later on.

you can validate the first one using "ps axuw -L" which shows all threads, along with 
their states. if that's the case, the only way to solve this is to split the blocking portion
into a separate syslog-ng process.

to diagnose the other, we need further information:
  * it'd be useful to check what syslog-ng is doing in its main thread using strace
  * it'd also be useful to check where each thread is by printing a backtrace for each thread in gdb


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