Dan Nicholson wrote:
I strongly suspect you're dealing with https://bugzilla.redhat.com/show_bug.cgi?id=2056090. I.e., autofs
Thanks a lot, Dan! So I guess the patch was rejected upstream?
doesn't handle mount namespaces. Since systemd uses lots of mount namespaces, the idle timeout essentially doesn't work. The only workaround I'm aware of is to run something in the root namespace that keeps the mount active. Having an active process with its current directory in the mount would do it.
But what I don't get: when I try to umount the users home manually during the minute we are waiting for the idle-timeout, it says "busy" and refuses the umount. But when the idle-timeout hits, it first kills the user session and then unmounts. Why does it kill the user session? If autofs thinks the mount was idle, why doesn't it just try to unmount and gets "busy"? Killing the user sessions is like "Oh, that mount is idle, I umount it, but, hmm, there are processes still using it, so I kill these first, although theses processes show me that the mount is not idle"... -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
