3 ms·
That post is confusing problem with solution. When you lose your ssh connection you are not logging out on purpose. Even ssh can help you there, though. You can
by erikb 10y ago
That post is confusing problem with solution. When you lose your ssh connection you are not logging out on purpose. Even ssh can help you there, though. You can configure ssh clients (and also servers I believe) to survive a session to be gone for minutes, even hours if you desire.
So your problem is that you haven't spent enough time learning to configure your ssh according to your needs. The cool thing is that ssh configs can be done for a specific session (if it happens just once in a while or you experiment about the right configuration), it can be done per target (in case you want to react differently on your personal blog and your company development host), and globally (to apply always). Have fun reading. You may find that ssh can solve a lot of problems and in some people's mind even solves problems like other tools but more elegant (I personally prefer it over http-proxys and VPNs as well).
- jdbernard 10y agoNo. 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.
- erikb 10y agoYes 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.
- jdbernard 10y agoHow 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.