On 2010-11-26 12:36:31 +0100, Kay Sievers wrote:
On Fri, 2010-11-26 at 12:04 +0100, Joachim Schrod wrote:
Kay Sievers wrote:
- 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.
Somebody needs to patch it, to accept socket activation, and write service files for it. Without that, it's not properly supported.
so does that mean that every service that doesnt have socket activation stuff will not be properly supported? i can imagine enough services where you dont want the delayed starts and all that. the only feature, that i really miss in SysV init atm, is service supervision. but one can easily get that with runit. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org