[dead]
Systemd Linger
11–20 of 96 posts
Re: Systemd Linger
#12I'm presumably missing something here. Why does tmux et al not work? Remotely? Ie you're logged in locally and remotely to the same machine, log out locally which kills everything running remotely, but then why would you log in twice like that?
And that being the case can systemd not just only close everything when your logins reach 0?
Re: Systemd Linger
#13I'm presumably missing something here. Why does tmux et al not work? Remotely? Ie you're logged in locally and remotely to the same machine, log out locally which kills everything running remotely, but then why would you log in twice like that? And that being the case can systemd not just only close everything when your logins reach 0?
You can detach from screen/tmux, leave it running in the background, and log back in later to the same screen/tmux like you left it.
Except systemd can kill it when you log out, so you come back to nothing.
Re: Systemd Linger
#14This is why i dislike systemd. Things not working the way I expect means I have to do more work to figure something out.
> Things not working the way I expect means I have to do more work to figure something out.
Sound like you don't like computers to begin with
Re: Systemd Linger
#15Default Debian Trixie out of the box configuration without changing any systemd config file allows gnu screen to work as it always has. There would have been great uproar and screeching if basic 'screen' detach and resume functionality had broken anywhere between Debian v11, v12 and v13, and it has not.
I'm assuming this is same for tmux but hasn't tested it.
Is there some major distro out there that has the config flag set the opposite of this by default?
Re: Systemd Linger
#16I'm presumably missing something here. Why does tmux et al not work? Remotely? Ie you're logged in locally and remotely to the same machine, log out locally which kills everything running remotely, but then why would you log in twice like that? And that being the case can systemd not just only close everything when your logins reach 0?
You can detach from screen/tmux, leave it running in the background, and log back in later to the same screen/tmux like you left it. Except systemd can kill it when you log out, so you come back to nothing.
Ah ok. Seems like the log out metaphor is kind of broken then?
It seems to me if you want persistence between logouts, the processes should belong to a different group/user.
(I'm spitballing hypotheticalshere, not saying anyone/thing in particular is wrong)
Re: Systemd Linger
#17This is why i dislike systemd. Things not working the way I expect means I have to do more work to figure something out.
> This is why i dislike systemd. Things not working the way I expect means I have to do more work to figure something out.
Even if the change is a genuine improvement?
Re: Systemd Linger
#18Default Debian Trixie out of the box configuration without changing any systemd config file allows gnu screen to work as it always has. There would have been great uproar and screeching if basic 'screen' detach and resume functionality had broken anywhere between Debian v11, v12 and v13, and it has not. I'm assuming this is same for tmux but hasn't tested it. Is there some major distro out there that has the config f…
> Default Debian Trixie out of the box configuration without changing any systemd config file allows gnu screen to work as it always has.
As mentioned in the second sentence of TFA. Debian enables linger by default.
Re: Systemd Linger
#19Systemd is simply too complex.
Re: Systemd Linger
#20Systemd is simply too complex.
Which part? Just saying systemd is like saying a distribution is too complex