https://bugzilla.novell.com/show_bug.cgi?id=656259
https://bugzilla.novell.com/show_bug.cgi?id=656259#c18
--- Comment #18 from Kay Sievers
Third-party scripts run in compat mode and can not make use of socket-activation.
They can, they do already, and it works well.
That's really not the point. The goal is to clean up the mess here, not to add more hacks.
(In reply to comment #14)
One of the main goals of systemd is to get rind of the piles of crap accumulated in sysv scripts and /etc/sysconfig/. The SUSE syslog script is a fine example of what we really don't want to see anymore.
But you'll see it on 11.4 :-)
Sure, no problem. We don't have to touch it, it should work. rsyslog has all merged upstream, can disable the sysv script, and is expected to work properly with the provided native systemd service files. The other syslogs probably work fine in compat mode. We might just don't get early boot messages and have no race-free syslog restart.
We may either write a /sbin/syslog-daemon wrapper in C allowing to switch between the daemons or adopt all syslog daemon packages to conflict with each other so every one can install a syslog.service file.
We really don't want legacy scripts wrapping services along with socket-activation. It's a complete backwards idea.
These 2 functions are *required* to implement this functionality in Type=forking service.
Systemd-patched/aware services should never fork. That's only there to support legacy services, which don't use socket-activation.
When you don't like it, we can also revert all the changes in all the syslog-daemons and wait until there is a lib providing this functionality.
See also comment 7.
There is no lib so far. We might get there, but not now. Most stuff is already merged upstream. When the time comes we can update the stuff, for now there is no library, and SUSE will not create one on their own.
Please use the old sysv scripts and leave the limited functionality as it is,
There is _no_ limited functionality. The socket activation works out-of-the box with the init script -- you'd see it, when you'd read the lsof output in bug 656104 comment 21 I mentioned above.
Sure, but it's not the way we like it to have. We really don't run sysv scripts combined with socket activation.
or use native service files if systemd features are wanted.
Definitively not for 11.4, see above.
Sure, no problem.
All this systemd stuff were requested far too late to make such intrusive changes.
Maybe. I didn't "request" anything. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.