Re:Systemd developer asks tmux to add systemd specific code
by jdbernard on Sunday May 29, 2016 @06:49PM
(#11798584)
No. I often purposefully log out of an SSH session and expect to come back later and have my tmux session still the same. Sometimes I log out of my desktop at home that I'm physically at, get to someplace else, log in via SSH, and reconnect to the same tmux session I had running when I was at home. This is one of the primary features of tmux. It's not about misconfigured SSH sessions.
[ Parent
| on HN ]
Re:Systemd developer asks tmux to add systemd specific code
by erikb on Monday May 30, 2016 @03:51AM
(#11800133)
Yes you are right. In that case you have tmux to keep your session. If it doesn't do it, it's pretty much tmux's fault. I understood the previous message as if losing the connection on a train ride would be the main issue.
Re:Systemd developer asks tmux to add systemd specific code
by jdbernard on Monday May 30, 2016 @10:14AM
(#11801437)
How is it tmux's fault when it is systemd that is killing processes? Tmux uses the standard mechanism to inform the system that it should live on, systemd no longer respects that mechanism.