On Tuesday 18 March 2014 10:02:43 Carsten Pfeiffer wrote: > On Tuesday 18 March 2014 02:36:36 Michael Schuerig wrote: > > Anyway, there are no discernable accesses by any KDE component. The > > fault is probably elsewhere. > > Then what happens if you test this with > - plain console > - a very simple session (fvwm + xterm)? On the console and in a KDE session for a freshly created user, the NFS is automatically unmounted when the timeout expires. In my usual KDE session, if I kill plasma-desktop, the timeout works, too. Restarting plasma-desktop causes the share to be automounted again, ie, without any explicit access to it. Here's what the pstree output for plasma-desktop looks like: plasma-desktop ├─ksysguardd ├─{KCupsConnection} ├─{QInotifyFileSys} ├─{QProcessManager} └─{plasma-desktop} I've also tried strace'ing plasma-desktop (with -e trace=open and with grepping for relevant paths), but didn't see any accesses to the share there. As I wrote in another reply, I was hoping to get some insight from autofs. Presumably it needs to know about which accesses and processes keep a mounted share from timing out. Unfortunately, even at debug level, no such information is in the log. Michael -- Michael Schuerig mailto:michael@schuerig.de http://www.schuerig.de/michael/
Attachment:
signature.asc
Description: This is a digitally signed message part.