Am 13.04.2025 um 15:24 schrieb Marc Haber:
On Sat, Apr 12, 2025 at 03:40:54PM +0200, Michael Biebl wrote:Would ConditionUser=!@system be an option here for those user services?my ansible user is not in the system user range, but still a system user, as it doesn't originate from a package.
That's a bit weird. If it's not in the system range, I personally wouldn't consider it a system user.
I'd really like the socket unit to be stopped on logout.
The systemd --user instance should be stopped when the user logs out, or rather when the last user session ends (a user could be logged in multiple times and the systemd --user instance is refcounted so to speak).
Things that can prevent that: - lingering is enabled for that account https://wiki.archlinux.org/title/Systemd/User#Automatic_start-up_of_systemd_user_instances - Some process(es) refuse to die on logout and keep the session active.Debian disables automatic killing of processes on logout, i.e. it defaults to KillUserProcesses=no
https://wiki.archlinux.org/title/Systemd/User#Kill_user_processes_on_logoutYou can either enabled that option or investigate which program keeps the session active.
Michael
OpenPGP_signature.asc
Description: OpenPGP digital signature
