[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
----------------------------------------------------------------------------
         Resolution|                            |INVALID
             Status|NEW                         |RESOLVED




--- Comment #6 from Balazs Scheidler <bazsi at balabit.hu>  2011-11-12 13:15:34 ---
Reading your diagnosis it seems that the D state applies to the whole process, 
therefore even if only one thread is in an uninterruptible sleep, the whole process with all other
threads will be suspended too.

This means that you'll need to run two syslog-ng processes to solve this:
  - one that is unlikely to become blocked by invalid I/O (e.g. with network destination)
  - another one that writes stuff to the local disk (e.g. with the file destinations)

One instance can pass messages to the other using unix domain sockets or pipes. In your situation 
the first one should read the local logs and pass them on to the 2nd process. This would ensure that
you get messages via the network with better probability.

Sorry, I'm setting this again to INVALID, as I don't intend to change syslog-ng to 
use a multi-process architecture, certainly this can be done with the configuration
outlined above.


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