On Sat, 12.03.11 00:15, Michael Biebl (mbi...@gmail.com) wrote: > > 2011/3/11 Andrey Borzenkov <arvidj...@mail.ru>: > > On Fri, Mar 11, 2011 at 9:10 PM, Mike Kazantsev <mk.frag...@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?
Nope. There's nothing magic that pulls syslog.target in. > That said, I agree that rsyslog.service should be pulled in via > syslog.target.wants and not multi-user.target.wants. Hmm, as mentioned the current thinking there is to hook as little into the targets as necessary to fulfill what they are needed for. And that is for syslog.target just syslog.socket, not the full rsyslog.service which can start much later. But I am a bit torn about this. It might be worth changing this. Dunno. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
