Hello, On 11/26/2010 03:02 PM, Marius Tomaschewski wrote:
Am Freitag, 26. November 2010 12:04:46 schrieb Joachim Schrod:
Kay Sievers wrote:
Hi,
- sort out the mess in /etc/init.d/syslog - probably just provide native service file for rsyslog, and disable the this weird script - systemd wants a syslog with socket activation, upstream rsyslog supports this already
Is syslog-ng support planned, too?
I find the possibility to select a syslog daemon of my choice extremely helpful and it would be sad to be reduced to rsyslog only.
Don't worry.
We will keep the choice and implement it for syslog-ng and syslogd as well. Looking at the patches in rsyslog, it is quite straight forward to do it.
May I ask you to implent it for syslog-ng 3.2? That's what I'd like to push into openSUSE 11.4 next week, and 3.1 is feature frozen upstream anyway. A package from 3.2 beta1 is available at https://build.opensuse.org/package/show?package=syslog-ng32&project=home%3Aczanik%3Asyslog-ng32 It currently fails to compile due to libnet changes. I'll fix that and update to latest git (which should not change much until the 3.2 release...) Bye, -- Peter Czanik (CzP) <czanik@balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org