If the behavior is truly random, I would be surprised, and I would say that there is a highly critical bug.
It would really help if you could perhaps help identify the pattern...
Currently, umount.ecryptfs_private is called any time a PAM session end event occurs.
This could be:
* logging out of an ssh session
* logging out of a graphical desktop session
* logging out of a a console session
This is, however configurable. Simply remove the file ~/.ecryptfs/auto-umount. Try removing that file and see if this is an acceptable solution to your problem.
Perhaps you have some semi-regular event that is logging in/out of your system? A remote cronjob ssh'ing in, perhaps?
Hi Daniel-
If the behavior is truly random, I would be surprised, and I would say that there is a highly critical bug.
It would really help if you could perhaps help identify the pattern...
Currently, umount. ecryptfs_ private is called any time a PAM session end event occurs.
This could be:
* logging out of an ssh session
* logging out of a graphical desktop session
* logging out of a a console session
This is, however configurable. Simply remove the file ~/.ecryptfs/ auto-umount. Try removing that file and see if this is an acceptable solution to your problem.
Perhaps you have some semi-regular event that is logging in/out of your system? A remote cronjob ssh'ing in, perhaps?
:-Dustin