https://bugzilla.novell.com/show_bug.cgi?id=656259
https://bugzilla.novell.com/show_bug.cgi?id=656259#c21
--- Comment #21 from Marius Tomaschewski
(In reply to comment #17)
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.
No, the point is that you don't read what people are writting to you. As I wrote, we'll not change the the syslog-daemon switch for 11.4. It was simply far too late to make all these update-intrusive changes as required, because systemd didn't worked reliably until end of 2010. And also, because you still didn't fixed this bug (even the library exists, but is simply not installed).
(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.
Nonsense. You still didn't read the comments in the bug reports, but just blame all people they're doing "crap" and "mess". So read this here please: All 3 syslog daemons (syslogd,syslog-ng and rsyslog) natively support systemd socket activation: - in "Type=simple" as well as in "Type=forking" systemd.service(5) mode and - for all unix dgram sockets systemd provides to them (that is also for the $chroot/dev/log sockets). We've added the required functionality to all of them upstream. The code required to implement the "Type=forking" is attached in comment #9. _Please_ forward it upstream and ship install the lib providing it. All patches are upstream - usually in git master, but our packages include these patches.
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.
And I'll really not change the syslog-daemon switch for 11.4, because it is too late due to systemd problems until end of 2010 and the change of the syslog daemon switch is very intrusive. Perhaps you didn't noticed, but we've released RC1 already. For 12.0 (or whatever follows the 11.4), we can change the daemon switch.
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.
systemd supports also socket activation in Type=forking services mode.
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.
And until there is a stable systemd lib, we'll not change the syslog daemon switch.
All this systemd stuff were requested far too late to make such intrusive changes.
Maybe. I didn't "request" anything.
There are (multiple AFAIS) feature requests to integrate systemd and you are assigned as developer for them. further, *you* asked to adopt the syslog daemons. -- 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.