ecryptfs being unmounted while user is still logged in

[Roland Hieber]

Hi,

lately I'm having problems with my ecryptfs home directory, which is
being unmounted while I'm still logged in and working on my machine. It
seems to be unmounted at around 0:00 every night, which has the effect
that some of my running applications stop working until I mount it again
using ecryptfs-mount-private, but even then, not all applications work
flawlessly (e.g. my awesome window manager won't spawn new urxvts,
manually started terminals show "(unreachable)" as current directory).

Unfortunately, I cannot find anything related in /var/log/*, but I have
the feeling that it has to do with my recent switch to systemd-sysv. Is
there maybe a daemon in userspace, which I forgot to start, that keeps
track of running logins or something? What can I do to debug this?

Related information:
$ uname -a
Linux r2d2 3.13-1-amd64 #1 SMP Debian 3.13.7-1 (2014-03-25) x86_64 GNU/Linux

$ apt-cache policy ecryptfs-utils systemd-sysv
ecryptfs-utils:
Installed: 103-3
Candidate: 103-3
Version table:
*** 103-3 0
200 http://ftp.de.debian.org/debian/ testing/main amd64 Packages
170 http://ftp.de.debian.org/debian/ sid/main amd64 Packages
100 /var/lib/dpkg/status
systemd-sysv:
Installed: 204-8
Candidate: 204-8
Version table:
*** 204-8 0
200 http://ftp.de.debian.org/debian/ testing/main amd64 Packages
170 http://ftp.de.debian.org/debian/ sid/main amd64 Packages
100 /var/lib/dpkg/status

Regards,
Roland Hieber

[Roland Hieber]

Post by Roland Hieber
Unfortunately, I cannot find anything related in /var/log/*, but I have
the feeling that it has to do with my recent switch to systemd-sysv.

For the record, purging systemd-sysv and installing sysvinit-core again
got rid of that nasty bug. I would like to file a bug report, but I'm
not sure which package is really at fault here – systemd or ecryptfs?

I also looked through all the crontabs installed on my system, nothing
there is executed at 0:00, but the filesystem gets unmounted exactly at
0:00, so it cannot be cron's fault.

- Roland

[Slavko]

Ahoj,

Post by Roland Hieber

Post by Roland Hieber
Unfortunately, I cannot find anything related in /var/log/*, but I
have the feeling that it has to do with my recent switch to
systemd-sysv.

For the record, purging systemd-sysv and installing sysvinit-core
again got rid of that nasty bug. I would like to file a bug report,
but I'm not sure which package is really at fault here – systemd or
ecryptfs?

You can fill bug against ecryptfs. If maintainer (or someone other) to
decide that this is needed, it can be reassigned to another package...

regards