On Thu, Aug 17, 2017 at 9:27 AM, Per Jessen <per@computer.org> wrote:
Moving to that directory does not cause it to be mounted.
Did you try 'ls' ?
Yes. Even though the unit files were in place, it required a reboot for the mounts to happen. "systemctl reload autofs" had no effect.
Odd that it is listed twice.
automount and mount - I think 'automount' is the unit that drives 'mount'.
Anyway, check /var/log/messages for systemd output related - you should see why your mtpt wasn't mounted.
It doesn't say anything. It just didn't happen until after the reboot. When autofs fails, you get an error and the message that the directory does not exist. This is good so you know that you are really accessing what you expect. systemd said nothing. I was in an empty directory (e.g. the mount point). This is especially troublesome when doing something like a backup that is expected to be on the mounted volume - not the disk containing the mount point. This is not a big issue. I am just trying to decide on moving things from autofs to systemd. I like the idea of all the mounts being in one file. But autofs has been working fine. A reboot is not really an issue. These things on my system are rather stable over time. The question is if we move to using systemd for this in our product systems... It would still be interesting to know the expected (i.e. systemd official) series of events that lead from editing /etc/fstab to the edits being used. Thanks for all the help to everyone who responded. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org