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

[bugzilla at bugzilla.balabit.com]

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





--- Comment #11 from Balazs Scheidler <bazsi at balabit.hu>  2011-12-21 14:26:30 ---
It might very well happen that the main thread is also invoking some syscalls on the 
monitored files as the code wasn't audited for this kind of usage.

I'm afraid doing this in a way that meets your requirements is going to be very 
fragile and would be often broken as features get added (and new syscalls added 
to non-worker-thread code)

It might be doable now to delegate all I/O operations to the worker threads, 
but keeping such a rule in mind while coding gets faded away fast, and might 
once make a feature impossible to implement.

Testing it is not easy either. I could integrate patches if they are not very intrusive,
but you'd probably have to care about keeping this feature working as I quite possibly wouldn't 
be enough alone. This feature is only useful when it doesn't break every-now-and-then.

All this boils down to is that I can't promise anything, but if patches are available and
you do regular testing of this specific feature I would do my best, which would probably
mean breakage every once in a while and might intentionally be broken if implementing a 
new feature would be much more expensive with this rule in mind.

Please let me know what you think.


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