4 ms·
When I connect to remote servers over SSH, I usually start a screen (another alternative is tmux) session and then perform my administrative and diagnostics act
by solarengineer 5y ago
When I connect to remote servers over SSH, I usually start a screen (another alternative is tmux) session and then perform my administrative and diagnostics actions in that session. This way, even if I get disconnected, I can reconnect and join that running session. There are other benefits to a screen multiplexer - such as multiple remote users being able to attach to the same session, a joy when a distributed team needs to diagnose an issue or watch some actions together.
- jefftk 5y agoCombine with mosh and you can even keep editing while the connection blips!
- iotku 5y agoYou may also want to look into mosh [1] as it will handle dropouts and continue where ssh would just fail on its own. Also has local echo for points of high latency. Was a real life saver on some of the terrible sat connections of yesteryear. 1. https://mosh.org/ https://mosh.org/
- aruggirello 5y agoHow does it compare to autossh?
- wffurr 5y agoautossh just re-reestablishes your ssh connection. It doesn't tolerate packet loss very well or have local echo like mosh. mosh does require UDP ports, though, which might be problematic with some firewalls or proxies.
- starfallg 5y agoMosh is great, but if you don't need the predictive terminal emulation, then you can try Eternal Terminal, which is easier to get running due to not needed an UDP port open.
- taf2 5y agoyeah i use screen for everything too... still there are times when a connection dropping is a bit scary...