Bug#756903: systemd: Boot hangs if filesystems unavailable

Cameron Norman camerontnorman at gmail.com
Mon Aug 4 00:36:27 BST 2014



El dom, 3 de ago 2014 a las 3:44 , Marco d'Itri <md at Linux.IT> escribió:
> On Aug 04, Cameron Norman <camerontnorman at gmail.com> wrote:
> 
>>  With mountall/Upstart, there is a nobootwait option supported. I 
>> believe the behavior is similar to nofail, except that mountall will 
>> emit the filesystem event before finishing mounting the filesystem 
>> as well as not GAF about success/failure. Do you know if systemd 
>> supports this? To implement this in systemd I believe you would make 
>> the generator for mount units from fstab not add 
>> Before=local-fs.target or Before=remote-fs.target if the nobootwait 
>> option is used. This solves the problem that systemd does not know 
>> which filesystems are essential or not.
> Such an option would not be the default, and if you can change your 
> configuration to use it then you can more easily fix your fstab as 
> well.

What do you mean by "fix your fstab"? Adding this option is even 
beneficial if there is nothing wrong with the fstab, as services can be 
started before non-essential fs's are up.

Thanks,
--
Cameron
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140803/e31cd9db/attachment-0002.html>


More information about the Pkg-systemd-maintainers mailing list