On 16/08/17 01:08 PM, Roger Oberholtzer wrote:
But systemd doesn't read and act on /etc/fstab.
In fact I think it does: man systemd.automount
I think that (a) you are behind on my exchange with Per and the test sequence I've suggested, what to look at and how systemd actually works and what it does; and (b) being a bit loose with language. Ultimately there is the /usr/sbin/automount program that the autofs.service unit directs the relevant parts of system (perhaps via you giving a systemctl command) to start (on boot) or restart. As far as I can tell, what you've been doing, what Per has been doing, is generating a new dot-mount file under /run/systemd/generator but never doing a restart of the autofs via the autofs.service with systemctl. Unless and until the running autofs re-reads the map noting is going to happen. <quote src=AUTOMOUNT(8)> NOTES If the automount daemon catches a USR1 signal, it will umount all currently unused autofs managed mounted file systems and continue running (forced expire). If it catches the TERM signal it will umount all unused autofs managed mounted file systems and exit if there are no remaining busy file systems. .... The daemon also responds to a HUP signal which triggers an update of the maps for each mount point. </quote> Unless you (stop & restart) or reset the deamon with a HUP signal, its not going to do anything about the changes propagated down from /etc/fstab. In effect doing a 'systemctl daemon-reload' does not do a 'systemctl reload *'. This is in accordance with the man page on the 'reload' option for systemctl: This command should not be confused with the daemon-reload command. What you want is to follow up with a systemctl reload autofs.service -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org