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

[bugzilla at bugzilla.balabit.com]

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

           Summary: --worker-threads=0 support
           Product: syslog-ng
           Version: 3.3.x
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: unspecified
         Component: syslog-ng
        AssignedTo: bazsi at balabit.hu
        ReportedBy: arekm at maven.pl
Type of the Report: enhancement
   Estimated Hours: 0.0


Hello,

I was hoping that threading support would solve my problem described
in https://bugzilla.balabit.com/show_bug.cgi?id=113.

Unfortunately it looks like it is impossible to create configuration for which
each target will use one thread by default (as only such configuration
is safe in case of some targets blocking on I/O).

This feature request is about adding some option like:
--worker-threads=0
that would limit number of threads to numer of sources + number of destinations,
so each possible blocking I/O would be happening in separate thread.

Yes, it would be more than cpu cores but this configuration is about
reliability and not performance.


(right now I have only one, network logging target that needs to always work,
so probably disabling threading globally and enabling threading only for this
network target would get me "always working" logging via net, even if some
infinite I/O blocking happens. What would be best is to have ability to have such
config on by default for all targets)


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