Comment 6 for bug 1855318

I have been trying to recreate in different permutations and I have come to the conclusion that the 2 weird mounts aren't the primary issue. Those are strange, but it appears to break when the autofs is started and stopped multiple times as it would be if someone were trying to troubleshoot there configuration.

It appears that the daemon does not clean up when it closes and can sometimes leave open mounts That should be closed. I found that if I stopped the daemon and restart, my configured mounts were not being mounted automatically.

When this happens, the happy path only returns when I close the deamon and manually release any held mounts.

To recreate the error:
1. I ran the daemon in debug mode in the foreground
2. navigated to OR did an "ls" on an automounted mount to verify that it was mounted
2.1 close any open file explorer windows
2.2 cd out of any mounted directories on the command line
3. After confirming the mount, I then manually close the running automount daemon
4. If I restart the automount daemon at this point, it does not consistently re-mount my configured mounts

This is where it is easy to assume that the 2 unconfigured mounts initially reported are the symptoms of the failure. It appears that automount does not cleanly close out in such a way that it can be restarted without manual intervention. This may be known/inherited bugginess of automount, and if so, maybe not a severe issue is being reported here.

Still no explanation for the 2 unconfigured mounts though. That is still valid unexpected behavior, whether the OS has autorun support or now.