2011/3/16 Lennart Poettering <[email protected]>: > On Sat, 12.03.11 01:14, Michael Biebl ([email protected]) wrote: > >> >> 2011/3/12 Michael Biebl <[email protected]>: >> > 2011/3/11 Andrey Borzenkov <[email protected]>: >> >> On Fri, Mar 11, 2011 at 9:10 PM, Mike Kazantsev <[email protected]> >> >> wrote: >> > >> >> >> >>> Btw, rsyslog.service seem to be installed into multi-user.target.wants, >> >>> why not syslog.target, which seem to indicate the point where proper >> >>> syslog daemon is running (according to systemd.special(7))? >> >>> >> >> >> >> Actually good question (same as for portmap) - who should pull in >> >> syslog.target then? >> > >> > Yeah, I noticed this myself already. Quite a bit of syslog output >> > ended up in /proc/kmsg during boot because rsyslog was started rather >> > late (via multi-user.target). >> > Afaics, there is not explicit symlink pulling in syslog.target, so I >> > assume it is handled internally by systemd. Lennart? >> >> Turns out, that indeed syslog.target is not automatically started. >> I symlinked syslog.target into multi-user.target.wants and >> rsyslog.service into syslog.target.wants. >> >> Now all services with After=syslog.target are correctly started after >> rsyslog.service. >> >> Lennart, I think we should add those changes to systemd and rsyslog.service. > > I think we should pull in rsyslog.target by default, but I am not
Will that ensure that rsyslog is started before services using After=syslog.target? > convinced that rsyslog.service should hook itself into syslog.target. > What is syslog.target then good for? Reading trough the systemd.special man page it says that syslog.target is the place where the real syslogd should be symlinks into. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
