On Fri, Mar 12, 2021 at 10:34 AM Ulrich Windl <[email protected]> wrote: > > >>> Reindl Harald <[email protected]> schrieb am 11.03.2021 um 16:23 in > Nachricht <[email protected]>: > > > > > 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 > > So journald is not listening to the syslog socket? So how are messages sent to > the journal in a compatible way?
https://www.freedesktop.org/wiki/Software/systemd/syslog/ > At least the manual page for syslog.socket is confusing then. > > Regards, > Ulrich > > > > > it's where early‑boot stuff comes from > > _______________________________________________ > > systemd‑devel mailing list > > systemd‑[email protected] > > https://lists.freedesktop.org/mailman/listinfo/systemd‑devel > > > > _______________________________________________ > systemd-devel mailing list > [email protected] > https://lists.freedesktop.org/mailman/listinfo/systemd-devel _______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
