Re: systemd, fstab, noauto and nofail
2014-11-22 22:10 GMT+01:00 Simon McVittie <smcv@debian.org>:
> On 22/11/14 19:54, Matthias Klumpp wrote:
>> (Maybe systemd has smarter methods for that case which I don't know of)
>
> I think RequiresMountsFor is what you're looking for.
>
> ConditionFileExists is not the right thing here: the Condition* family
> more or less means "if the condition is absent, behave as if all the
> Exec* were /bin/true". It's a way to do things like skipping a one-time
> initialization unit if a flag-file exists, or skipping a virtualization
> helper unless systemd is running inside the appropriate technology, or
> whatever.
>
> RequiresMountsFor means "however desirable it might be, this unit isn't
> going to work unless the mountpoint ancestors of all these paths exist".
That is very good to know, thank you! (I fortunately used the "wrong"
solution only temporarily to debug a startup issue)
Looks like nothing speaks against starting ssh as early as possible on
systemd systems then.
Reply to:
- References:
- Bug#769907: general: non-sysvinit init systems are made of fail
- From: Michal Suchanek <hramrach@gmail.com>
- Re: Bug#769907: general: non-sysvinit init systems are made of fail
- From: Noel Torres <envite@rolamasao.org>
- Re: systemd, fstab, noauto and nofail
- From: Simon McVittie <smcv@debian.org>
- Re: systemd, fstab, noauto and nofail
- From: Noel Torres <envite@rolamasao.org>
- Re: systemd, fstab, noauto and nofail
- From: Russ Allbery <rra@debian.org>
- Re: systemd, fstab, noauto and nofail
- From: Adam Borowski <kilobyte@angband.pl>
- Re: systemd, fstab, noauto and nofail
- From: Russ Allbery <rra@debian.org>
- Re: systemd, fstab, noauto and nofail
- From: Jonas Smedegaard <dr@jones.dk>
- Re: systemd, fstab, noauto and nofail
- From: Russ Allbery <rra@debian.org>
- Re: systemd, fstab, noauto and nofail
- From: Matthias Klumpp <matthias@tenstral.net>
- Re: systemd, fstab, noauto and nofail
- From: Simon McVittie <smcv@debian.org>