[X2Go-Dev] Bug#1198: loginctl enable-linger
On 08/11/2017 03:59 PM, Orion Poplawski wrote: > There is also "systemd-run", not sure how that compares. systemd-run is changing the unit type in which context a command is executed. By default, commands are executed in a session context. With systemd-run, that can be changed to scope, service or timer-scheduled contexts. I don't think that makes sense in our case. A session context should be most appropriate to what we do. Changing the context also won't help us with lingering, as far as I can see, since such scope/service/timer contexts are also killed automatically once the last user login vanishes. Mihai signature.asc Description: OpenPGP digital signature ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#1198: loginctl enable-linger
On 08/11/2017 08:53 AM, Mihai Moldovan wrote: > On 08/10/2017 04:07 AM, Orion Poplawski wrote: >> So I guess the fix for this is to run "loginctl enable-linger" in >> x2goruncommand? Do this seem correct? I'll go for x2gostartagent, though, since that's really the first process in our chain. Mihai signature.asc Description: OpenPGP digital signature ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#1198: loginctl enable-linger
So I guess the fix for this is to run "loginctl enable-linger" in x2goruncommand? Do this seem correct? See also https://bugzilla.redhat.com/show_bug.cgi?id=1478974 -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
