https://bugzilla.novell.com/show_bug.cgi?id=671525
https://bugzilla.novell.com/show_bug.cgi?id=671525#c26
--- Comment #26 from Kay Sievers
The question is: how can be determined to which process the socket belongs to ... systemd or one of the system loggers.
I don't think any tool should try to be smart here about the systemd bridge. The socket will always be owned by systemd and only possibly inherited from started services, which might be none, one, or several. A syslog without socket activation will probably just delete /dev/log and create its own. But we can't really support that longer-term. I thought you might know just what's the difference in the syslogs and the klogd message loop. It might not be worth investigating how the current syslog init magic and syslog-ng fails, and we better just go directly for native systemd service files, and make them working in a way systemd expects them to work. If there is no simple fix for the current syslog logic, feel free to assign it back to me, I'll probably not work on it anytime soon, but I can keep track of it. -- 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.