On 16/08/17 01:53 PM, Per Jessen wrote:
Anton Aylward wrote:
The best I can figure is that neither reload no reexec actually ends up restarting the automounter.
I don't believe the systemd auto-mount scheme needs a running task. I would expect systemd to run inotify() on the applicable mount points and kick off the (generated) units when a mount is needed.
Since, as I say, there doesn't seem to be a SIGCHLD to force a reread at the deamon, its going to take the restart.
You might have tried "systemctl stop autofs; systemctl start autofs" I think that's right.
'autofs' is the original automounter, not the systemd ditto.
*sigh* The way system service files work is that they execute some higher level command, possibly run some daemon. Take a look at what's in - smd.seerver - postfix.service - fetchmail.service - cups.service - sshd.service - sddm.service and so forth. And of course, autofs.service : [Unit] Description=Automounts filesystems on demand Documentation=man:automount(8) man:autofs(5) After=network.target remote-fs.target nss-lookup.target nss-user-lookup.target Before=systemd-logind.service [Service] Type=forking PIDFile=/var/run/automount.pid EnvironmentFile=-/etc/sysconfig/autofs ExecStart=/usr/sbin/automount $AUTOFS_OPTIONS -p /var/run/automount.pid ###### ^^^^^^^^^^^^^^^^^^^^ ###### Please note the above line ExecReload=/usr/bin/kill -HUP $MAINPID TimeoutSec=180 KillMode=mixed [Install] WantedBy=multi-user.target Of course you can verify that these things started by systemd because of the imperatives in the dot-service files are there and running with the 'ps' command. Contrary to myth and mis-information spread by denouncers, systemd is not some great super-program that is soaking up the function of everything else. -- 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