Quoting Dustin Kirkland (<email address hidden>):
> I'm marking confirmed, as I, too, have seen this from time to time in
> Byobu (gnu screen under the covers).
>
> Per discussion on the ecryptfs-users@ mailing list, we believe this has
> to do with the kernel's lazy unmount. Not sure where or how to fix it
> yet...
Well, the only way you could prevent this, if i'm thinking right, would
be for screen/byobu to bump the mount count. Screen does appear to
support pam, so you could have perhaps
Quoting Dustin Kirkland (<email address hidden>):
> I'm marking confirmed, as I, too, have seen this from time to time in
> Byobu (gnu screen under the covers).
>
> Per discussion on the ecryptfs-users@ mailing list, we believe this has
> to do with the kernel's lazy unmount. Not sure where or how to fix it
> yet...
Well, the only way you could prevent this, if i'm thinking right, would
be for screen/byobu to bump the mount count. Screen does appear to
support pam, so you could have perhaps
/etc/pam.d/screen:
session optional pam_ecryptfs.so inc_only
where inc_only would just bump the mount count on $HOME if that is
already mounted.
-serge