Looks like autofs needs to do 'stop on deconfiguring-networking'. That will ensure that the main process is completely stopped before the network is shutdown. I wonder if we should also consider raising the 'kill timeout' above 5 seconds, as it may take longer than that to unmount a lot of mounts, which could also explain the phantom mounts leftover, if the daemon was SIGKILL'd before it was done. Is it conceivable that these phantom mounts will be there even after autofs is completely shutdown in a graceful way?
Looks like autofs needs to do 'stop on deconfiguring- networking' . That will ensure that the main process is completely stopped before the network is shutdown. I wonder if we should also consider raising the 'kill timeout' above 5 seconds, as it may take longer than that to unmount a lot of mounts, which could also explain the phantom mounts leftover, if the daemon was SIGKILL'd before it was done. Is it conceivable that these phantom mounts will be there even after autofs is completely shutdown in a graceful way?