Bug#1008725: systemd-logind option KillUserProcesses=true kills mount.davfs of user mount units

[Michael Biebl]

Am 31.03.22 um 11:21 schrieb Andreas Feldner:

Package: systemd
Version: 250.4-1
Severity: normal

Dear Maintainer,

I activated KillUserProcesses=true for systemd-logind by creating a file
/etc/systemd/logind.conf.d/99-killuserprocs.conf with the content below.

Some users have user session mounts configured by a unit file
~/.config/systemd/user/home-user-some-path.mount with the content similar to 
below.

This leads to all stale user process being killed after logout, which
was basically the intention.

However, the user mount of type davfs also spawns a user process 
/sbin/mount.davfs
each. Apparently, these processes get killed as well before a proper unmount of 
the
user mounts. This leads to stale mount points and stale PID files requiring 
manual
removal by the user before the directory can be mounted again.

I would have expected that processes spawned by the mount unit file do not get 
killed
by the logind session but are handled with the life cycle of the mount unit.

https://github.com/systemd/systemd/issues

Regards,
Michael

I'd say what you see is expected behaviour. KillUserProcesses= is a blunt tool and simply kills all processes that are left-overs after a logout. Tbh, this feels like a bug in davfs. It should properly release its resources when being killed. That said, since Debian does not ship any custom patches in that regard, it's best if you raise this directly upstream at

OpenPGP_signature
Description: OpenPGP digital signature