4 ms·

UNIX was designed to run background processes and do offline computing. I log into multiple remote systems every day and connect to my ongoing tmux sessions in

by zik 10y ago

UNIX was designed to run background processes and do offline computing. I log into multiple remote systems every day and connect to my ongoing tmux sessions in other countries. This isn't exactly an unusual use case. Banning this is a big downgrade in functionality.

wallacoloo 10y ago
Yeah, I get this. I don't disagree that it shouldn't be possible to run persistent sessions. I think it's just an issue of me finding the terminology counterintuitive. > I log into multiple remote systems every day and connect to my ongoing tmux sessions in other countries. In this case, it sounds to me that you aren't logging out. It sounds like you're effectively just suspending the connection to your session and then coming back to it later. i.e. you didn't SSH in and then run 'exit' from within your sesson, right? Or is that indeed the way it's done?
- comex 10y ago
  Depends what you mean by 'session'. Unix has long had a concept of sessions, where the login shell will send SIGHUP to everything in the session when it exits; daemons like tmux (the server side) indicate their intent to start a separate session using setsid(). Apparently systemd has its own concept of session which is the same idea but completely separate, and requires some systemd specific magic to split off. Yay!
  - JdeBP 10y ago
    In fairness, X desktops have their own concepts of sessions that are not congruent with kernel sessions, similarly. * http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/windows-nt-session.html#UnixLoginSession http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/wi... * https://www.x.org/releases/X11R7.6/doc/man/man1/xdm.1.xhtml#heading3 https://www.x.org/releases/X11R7.6/doc/man/man1/xdm.1.xhtml#...
- wtallis 10y ago
  I'm not a tmux user, but what you describe is pretty much how it works for screen. You use a keyboard shortcut to detach from your screen session, then `exit` to terminate the login shell that ssh ran and close the ssh connection. Later, you can log back in through ssh or locally and run `screen -r` to resume the detached session.

by zik 10y ago

wallacoloo 10y ago

Yeah, I get this. I don't disagree that it shouldn't be possible to run persistent sessions. I think it's just an issue of me finding the terminology counterintuitive. > I log into multiple remote systems every day and connect to my ongoing tmux sessions in other countries. In this case, it sounds to me that you aren't logging out. It sounds like you're effectively just suspending the connection to your session and then coming back to it later. i.e. you didn't SSH in and then run 'exit' from within your sesson, right? Or is that indeed the way it's done?

comex 10y ago
Depends what you mean by 'session'. Unix has long had a concept of sessions, where the login shell will send SIGHUP to everything in the session when it exits; daemons like tmux (the server side) indicate their intent to start a separate session using setsid(). Apparently systemd has its own concept of session which is the same idea but completely separate, and requires some systemd specific magic to split off. Yay!
- JdeBP 10y ago
  In fairness, X desktops have their own concepts of sessions that are not congruent with kernel sessions, similarly. * http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/windows-nt-session.html#UnixLoginSession http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/wi... * https://www.x.org/releases/X11R7.6/doc/man/man1/xdm.1.xhtml#heading3 https://www.x.org/releases/X11R7.6/doc/man/man1/xdm.1.xhtml#...
wtallis 10y ago
I'm not a tmux user, but what you describe is pretty much how it works for screen. You use a keyboard shortcut to detach from your screen session, then `exit` to terminate the login shell that ssh ran and close the ssh connection. Later, you can log back in through ssh or locally and run `screen -r` to resume the detached session.