Re: [systemd-devel] Q; syslog.socket dependency
Am 11.03.21 um 12:17 schrieb Ulrich Windl: Hi! I have a unit that uses logger, and I want to run it after syslog is available. So I added syslog.socket as dependency, but it fails: Mar 11 12:11:02 jeos1 systemd[1]: syslog.socket: Socket service syslog.service not loaded, refusing. Mar 11 12:11:02 jeos1 systemd[1]: Failed to listen on Syslog Socket. Doesn't journald also "provide" syslog.socket? Manual says: syslog.socket The socket unit syslog implementations should listen on. All userspace log messages will be made available on this socket. For more information about syslog integration, please consult the Syslog Interface[2] document you need no dependencies for logging - journald is responsible for that and even available in the initrd it's where early-boot stuff comes from ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Q; syslog.socket dependency
On Thu, Mar 11, 2021, 13:17 Ulrich Windl wrote: > Hi! > > I have a unit that uses logger, and I want to run it after syslog is > available. So I added syslog.socket as dependency, but it fails: > Mar 11 12:11:02 jeos1 systemd[1]: syslog.socket: Socket service > syslog.service not loaded, refusing. > Mar 11 12:11:02 jeos1 systemd[1]: Failed to listen on Syslog Socket. > > Doesn't journald also "provide" syslog.socket? > Yes but no. "Syslog.socket" is specifically for internal forwarding *from* journald to an external syslogd. What you're looking for (the journald *input* socket that's used by other programs) is actually "systemd-journald-dev-log.socket". Usually there should be no need to explicitly order against it, as normal services are already indirectly ordered after sockets.target as a whole. You'll only need an After if you're using DefaultDependencies=no. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Q; syslog.socket dependency
Hi! I have a unit that uses logger, and I want to run it after syslog is available. So I added syslog.socket as dependency, but it fails: Mar 11 12:11:02 jeos1 systemd[1]: syslog.socket: Socket service syslog.service not loaded, refusing. Mar 11 12:11:02 jeos1 systemd[1]: Failed to listen on Syslog Socket. Doesn't journald also "provide" syslog.socket? Manual says: syslog.socket The socket unit syslog implementations should listen on. All userspace log messages will be made available on this socket. For more information about syslog integration, please consult the Syslog Interface[2] document. Regards, Ulrich ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
