Could someone clarify what is supposed to be standard syslog integration in systemd? I.e. am I right, that
- syslog.socket activates built-in systemd syslog implementation systemd-kmsg-syslogd which simply dumps everything to /dev/kmsg - at some point "real" syslog service is started which either takes over or creates new /dev/log. Is it correct? So questions 1. as there can be only one /dev/log socket activation, real syslog need not (and should not) supply it. It sould conflict with default syslog.socket. Am I right? 2. how can real syslog service "take over" /dev/log? Code example? I am not fond of idea to leave unused daemon hanging around. Thank you! _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
