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".
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.
Either one, since it doesn't know the cause it shouldn't try to remount. Accident or malice -- since it is unknown then the effect of remounting is unknown and further corruption occurs.
A systemd generation sysadmin will 'change state definition" and let the automounter do the unmount.
--- Change it how? from the command line? in 1 command specifying the device?
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.
---- If automounting was desired it would be in /etc/auto.xxx
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.
--- That is a bug and is not expected behavior. On *nix based systems, the files in fstab are mounted once. If you want automount behavior then put everything in /etc/auto.xxx, but don't try to change the established meaning of /etc/fstab.
What we have here is a paradigm shift....
No... it's broken behavior. /etc/fstab is not for automounted file systems. That's what /etc/auto.xxx is for. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org