,
5 tweets,
1 min read
Read on Twitter
Here's a little problem I run into all the time, and how I solve it.
I've SSH'd into a machine, started a long running process (let's say, nmap). Now I need to disconnect from SSH, but I want to keep the process running in a tmux/screen session? How do I do this? Read on! 1/x
I've SSH'd into a machine, started a long running process (let's say, nmap). Now I need to disconnect from SSH, but I want to keep the process running in a tmux/screen session? How do I do this? Read on! 1/x
First, I background the process by hitting Ctrl+Z, then keep it running by using the "bg" command, and disown it with "disown nmap". 2/x
Next I find the process ID using "ps auxw | grep nmap". Take note of it!
If I don't already have it, I install a neat little utility called reptyr. For Debian-based systems, you can usually just:
sudo apt install reptyr
I open a tmux/screen session with "tmux" or "screen" 3/x
If I don't already have it, I install a neat little utility called reptyr. For Debian-based systems, you can usually just:
sudo apt install reptyr
I open a tmux/screen session with "tmux" or "screen" 3/x
Then, within the tmux/screen session, I take control of the job with "reptyr <process id>".
Nice! 4/4
Nice! 4/4
Just for all the people saying "Well actually, you can just start it in tmux"... this is meant to be used when you didn't start the process in tmux, and now you want it to be in tmux.
