Comment by benj111

2 days ago

I'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?

6 comments

benj111

Reply
tux3  2 days ago

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.

  • c-hendricks  2 days ago

    What I don't get is why (on Arch) I have linger off yet have never had trouble with tmux/ zellij being killed.

    Edit: ah, this post clears it up. Mentions linger has nothing to do with screen muxers, and also brings KillUserProcesses to peoples attention.

    Damn systemd and its multiple levels of convenience.

  • benj111  2 days ago

    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)

    • dietr1ch  2 days ago

      Think about user services in a multi-user setup

      Do you want user-level services, or a multi-tenant system-level service? - Who can tweak the service configuration? - How do you ensure there's no data leaks between users? - What about misbehaviour? Quotas, crashes

      I think lingering is great here

      1 reply →