[systemd-devel] [PACKAGERS] rsyslog and systemd

Michael Biebl mbiebl at gmail.com
Tue Mar 15 23:17:20 PDT 2011

2011/3/16 Lennart Poettering <lennart at poettering.net>:
> On Sat, 12.03.11 01:14, Michael Biebl (mbiebl at gmail.com) wrote:
>> 2011/3/12 Michael Biebl <mbiebl at gmail.com>:
>> > 2011/3/11 Andrey Borzenkov <arvidjaar at mail.ru>:
>> >> On Fri, Mar 11, 2011 at 9:10 PM, Mike Kazantsev <mk.fraggod at gmail.com> 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

> 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.


Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

More information about the systemd-devel mailing list