HI..

I did go ahead and create a systemd script that runs at boot time to clear the linger folder out and recreate the session database.

Any other thoughts on this?

Thanks

Rob

From: Mike Gabriel Sent: Wednesday, October 23, 2019 3:38 PM To: Montjoy, Robert (montjoy) Cc: x2go-dev@lists.x2go.org Subject: Re: [X2Go-Dev] loginctl 'enable-linger' causes systemd --user to respawn on boot

Hi Mihai, hi Robert,

On Mi 16 Okt 2019 22:11:37 CEST, Montjoy, Robert (montjoy) wrote:

Hi.

At one time "loginctl enable-linger" was added to the x2gostartagent to make sure the systemd did not kill the x2go process on disconnect. This has had the probably undesired affect of having systemd --user username being executed on boot for every x2go user. At the last boot about 70 processes (one for systemd and one for pam) were spawned. This is probably not what we want. Is there a better way to handle the systemd termination issue? Should something like

systemd-run --scope --user x2goagent .....

be used instead? Or can x2go cleanup this entry on termination? Maybe have x2gocleansessions do it?

Note: I will probably cleanup /var/lib/systemd/linger on boot by executing rm -f /var/lib/systemd/linger/* but that it is more of a "hammer" approach than anything else.

Thanks in advance.

Rob

@Mihai: Can you confirm this? This needs to be addressed as an important bug, I guess.

Mike

DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de