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. Cheers, Lorenz On Thu, Nov 19, 2015 at 2:40 PM, Michael Biebl <[email protected]> wrote: > Am 19.11.2015 um 14:29 schrieb Felipe Sateler: > > Control: tags -1 moreinfo > > > > On 19 November 2015 at 09:59, Lorenz Hübschle-Schneider > > <[email protected]> wrote: > >> Package: systemd > >> Version: 228-1 > >> Severity: critical > >> Justification: breaks the whole system > >> > >> Dear Maintainer, > >> > >> after the upgrade to systemd 228-1, my system failed to boot. It got > stuck in "Create Volatile Files and Directories...", which I cancelled > after a good minute. I had to downgrade systemd and related packages (udev, > etc) to be able to boot again. > >> > > >> I set the severity to critical as this seems to render systems > unbootable if /home is a network filesystem. I hope that's not too drastic. > > > > My guess is that the automount part is part of the problem here. If > > so, we should lower severity. > > It would also be interesting to at least let systemd-tmpfiles run for 90 > secs. > It might eventually time out and the boot continues. > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > >
