This is my new build go to package. Right behind vim and netstat.
Before running updates or big installs, get in to a tmux session. If your ssh session drops, it won’t interrupt the process.
If you want to see multiple servers/network devices, run the same commands, see the same output, switch on pane synchronization and run identical commands in all of them. Even password inputs when you run in to a sudo.
You can design layouts by percentage of the screen - 30%, 60% I’ve got three sites with redundant ISPs, 6 panes showing mtr sessions for each link, which work on any terminal size.
You can have someone else log in to the server and connect to the same tmux session as you, and show them what you’re doing and typing real time. Then collect the log afterwards.
I found a tmux session on a CentOS box that had been running for 5 years in the lab environment when I joined my current company - the guy who spawned it left 4 years ago.
It’s incredibly powerful.
Also, mtr-tiny is great for diagnosing latency issues
This is my new build go to package. Right behind vim and netstat.
Before running updates or big installs, get in to a tmux session. If your ssh session drops, it won’t interrupt the process.
If you want to see multiple servers/network devices, run the same commands, see the same output, switch on pane synchronization and run identical commands in all of them. Even password inputs when you run in to a sudo.
You can design layouts by percentage of the screen - 30%, 60% I’ve got three sites with redundant ISPs, 6 panes showing mtr sessions for each link, which work on any terminal size.
You can have someone else log in to the server and connect to the same tmux session as you, and show them what you’re doing and typing real time. Then collect the log afterwards.
I found a tmux session on a CentOS box that had been running for 5 years in the lab environment when I joined my current company - the guy who spawned it left 4 years ago.
It’s incredibly powerful.
Also, mtr-tiny is great for diagnosing latency issues