On Tuesday 28 October 2014, Anton Aylward wrote:
On 10/27/2014 11:45 AM, Carlos E. R. wrote:
This worked till systemd changed this particular behaviour and mounted automatically things that the administrator umounted. No matter what fstab says, if I, root, do "umount", I want it to stay till I "mount".
FYI I filed a bug report https://bugzilla.suse.com/show_bug.cgi?id=902612 But seems that they just defend this systemd "feature". Again ignoring the fact that any existing user would expect the old behavior ... that umount just works.
In this event, systemd is running an automounter and doing its best to maintain state. It doesn't know the sysadmin is a sysvinit generation guy and can't tell such a umount from a an accident or malice.
A systemd generation sysadmin will 'change state definition" and let the automounter do the unmount.
if this was a non-local disk and this was a nfs mount using the old, well recognized automounter, then you're recognise this behaviour for what it is.
As I keep saying, systemd is about DECLARATIVE not procedural management of the system. So long as the state tables, in this case /etc/fstab, DECLARE that the fs should be mounted, the automounter function will keep it mounted. That is the correct and expected behaviour.
There is a solution to get rid off systemd mount stupidity. kernel command line: fstab=no /etc/init.d/after.local: /usr/bin/mount -a I have not tested yet. Could be that there are drawbacks. But probably these drawbacks will be advantages too. :) cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org