Am 29.08.19 um 20:58 schrieb Dave Howorth: >> We do this for safety reasons. Please declare all your mounts as >> "nofail" and then systemd will boot up even without them being >> around. But of course things will fall apart badly then as soon as a >> device goes missing as all services will assume the file systems they >> need are there but potentially are just reading or writing to the file >> system undearneath. > > There's an easy way around that. Change the permissions of the mount > directory to be very restrictive, such that whatever normally writes in > the mounted filesystem/directory can't. Then it's up to applications to > deal with read or write failures appropriately.
i doubt that root owned prcoesses care about the permissions and the immutable bit is not useable for most people besides that it can lead to horrible errors set it to /etc/inittab and the next systemd-update will fail on fedora in a way that it's no longer in the rpmdatabase at all _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
