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