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
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
likesystemd-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
On 10/16/19 14:11, 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
I just noticed this issue on our systems. I think switching to systemd-run is likely the better way to go. The attached patch is what I am testing on our systems.
-- Orion Poplawski he/him/his - surely the least important thing about me IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 https://www.nwra.com/
-
Mike Gabriel -
Montjoy, Robert (montjoy) -
Orion Poplawski