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. 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. What we have here is a paradigm shift.... -- "Many people may listen, but few people actually hear." -- Harvey Mackay. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org