On Wed, Apr 20, 2011 at 01:22:32AM +0200, Lennart Poettering wrote:
> On Tue, 19.04.11 13:52, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
> > On Tue, Apr 19, 2011 at 12:15:01PM +0200, Mirco Tischler wrote:
> > Ok, now I'm starting with "systemd.unit=setup.service". There are some
> > issues however:
> > 
> > [...]
> > Starting Debug File System...
> > Starting /tmp...
> > Starting /var/log...
> > Starting Runtime Directory...
> > Starting Lock Directory...
> > Starting /var/tmp...
> > Starting Remount API VFS...
> > Starting File System Check on Root Device...
> > Starting Media Directory...
> > Starting Stdio Syslog Bridge...
> > <27>systemd-logger[234]: Failed to connect log socket to /dev/log: No such 
> > file or directory
> > <29>systemd[1]: systemd-logger.service: main process exited, code=exited, 
> > status=1
> > <29>systemd[1]: Unit systemd-logger.service entered failed state.
> > Starting Stdio Syslog Bridge...
> > <27>systemd-logger[246]: Failed to connect log socket to /dev/log: No such 
> > file or directory
> > <29>systemd[1]: systemd-logger.service: main process exited, code=exited, 
> > status=1
> > <29>systemd[1]: Unit systemd-logger.service entered failed state.
> > [...]
> > 
> > This looks like there is a dependency missing for systemd-logger.service,
> > right?
> 
> The logger service needs the kmsg-syslogd service around? Did you remove
> that from your build?

I found the problem:
systemd-logger.service has "After=syslog.socket" but no "Require". I with a
multi-user or graphical default target, this is handled via sockets.target.
I'm not sure what's the correct solution here?
If my special default target requires sockets.target, what does this mean
for e.g. sshd.socket etc.?

Regards,
Michael Olbrich

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to