I have a rather odd question to ask. I have an application (implemented in Golang CLI). I configured it to run as "startup application". The problem I'm having is, when I log out, the instance of this application is still running. And if I, say, log in/log out 5 times, I will end up with 5 copies of the app. I feel like I'm missing something very obvious. (I tried to run it directly, or via shell wrapper, the result is the same).
To summarize, how to make sure the app that starts when a user logs in dies when a user logs out?
The app is single-threaded (I do not create any go routines explicitly).
Cinnamon session and startup apps related question
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Cinnamon session and startup apps related question
Last edited by LockBot on Thu Feb 09, 2023 11:00 pm, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Cinnamon session and startup apps related question
The culprit is a default systemd setting:
+ file /etc/systemd/logind.conf
+ parameter: KillUserProcesses
+ default is "no"
Change it to KillUserProcesses=yes.
The changed setting will be used after the next reboot or after reloading systems.
Taken from here:
viewtopic.php?t=337393
+ file /etc/systemd/logind.conf
+ parameter: KillUserProcesses
+ default is "no"
Change it to KillUserProcesses=yes.
The changed setting will be used after the next reboot or after reloading systems.
Taken from here:
viewtopic.php?t=337393