Bug#805553: systemd 228-1 fails to boot: hangs in Create Volatile Files and Directories

[Michael Biebl]

Am 19.11.2015 um 14:54 schrieb Lorenz Hübschle-Schneider:
> I will try re-upgrading later this afternoon and let it run for a longer
> time, but the message was "$x sec / no limit".
> 
> Felipe, are you referring to /usr/lib/tmpfiles.d/home.conf? I will try that
> out as well.
> 
> With a normal mount I previously had cyclic dependency issues, as I want to
> bind-mount a local directory into that. It seems that this is wholly
> unsupported by systemd and I couldn't get it to work reliably, so now the
> bind mount is in /etc/rc.local as an ugly workaround. I can try making
> /home a normal mount again, but given that the issue seems to be a lack of
> network access, I don't see how that would succeed. I'll try to be sure
> though.

Btw, how do you configure your network? NetworkManager or ifupdown?

With ifupdown, the boot doesn't get stuck, but then, ifupdown runs in
sysinit.target.

I can confirm, that with 227, "v /home" does not trigger a mount request
and with 228 "Q /home" does.

On a cursory glance, I would consider this new behaviour a bug.


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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151119/e8a20286/attachment-0002.sig>