On Mon, Sep 26, 2016 at 4:20 PM, Xen <l...@xenhideout.nl> wrote: ... >> >> because earlier systems (sysvinit) hat no concept like emergency mode >> as they where a lousy bunch of scripts where you ended in case of a >> crucial disk failing in a undefined state? >> >> because earlier systems had no concept for "nofail" or "fail" at all > > > It is worth noting that nofail will have no effect if any services pull in > the mount target. >
What effect do you expect? If service Requires mount point and mount point is not available, service startup fails. That is correct and expected behavior. If service does not require mount point, service should be saying Wants and After. Which is at the end exactly what "nofail" does w.r.t. local-fs.target. So yes, "nofail" won't magically convert Requires into Wants for every service definition that mentions mount point. > I'm not sure if I can use nofail to disable swap service from being > activated, for instance. > > _______________________________________________ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
