I sometimes have long running processes that I want to kick off before going home, so I create a SSH session to the server to start the process, but then I want to close my laptop and go home and later, after dinner, I want to check on the process that I started before leaving work. How can I do that with SSH? My understanding is that if you break your SSH connection you will also break your login session on the server, therefore killing the long running process.
nohup to make your process ignore the hangup signal:
$ nohup long-running-process & $ exit
35This is it. No need to install screen or tmux. This is actually the good old way to do it. Sure 'screen' or 'tmux' are both wonderous apps and should be used when needed, but as simple as running a process in the background from which you can log out, go for the above.– reicheAug 14, 2010 at 11:40
4is nohup like disown?– cjacAug 15, 2010 at 9:12
45They have similar purposes, but they differ in many ways.
nohupintercepts SIGHUP so that when the shell that ran it quits and sends SIGHUP to all its still-running children,
disownsimply removes the specified job from Bash's child list, so it won't try to send SIGHUP at all.
nohupis a program separate from the shell, so it works with all shells, whereas
disownis a Bash builtin.
nohupaccepts the command to run, whereas
disownonly works after the job is started and you've backgrounded it so you can get back to the shell. Aug 15, 2010 at 14:00
3Awesome quick review for those who are unfamiliar with nohup and disown - as well as some easy ways to deal with terminal sessions serverwatch.com/tutorials/article.php/3935306/…– DanAug 12, 2014 at 21:58
tail -f nohup.outto check what's going on when you're back. Nov 3, 2016 at 15:15
You want to be using GNU Screen. It is super awesome!
ssh email@example.com screen #start a screen session run-a-long-process
CTRL+a , d to detatch from your screen session
exit #disconnect from the server, while run-a-long-process continues
When you come back to your laptop:
ssh firstname.lastname@example.org screen -r #resume the screen session
Then check out the progress of your long-running process!
screen is a very comprehensive tool, and can do a lot more than what I've described. While in a screen session, try ctrl+a,? to learn a few common commands. Probably the most common are:
- CTRL+a , c to create a new window
- CTRL+a , n to switch to the next window in your screen session
- CTRL+a , p to switch to the previous window in your screen session
- if you log in from a bunch of different systems, you may have accidentally left yourself attached to an active screen session on a different computer. for that reason, I always resume with
screen -d -rto ensure that if another shell is attached to my screen session, it will be detached before I resume it on my current system.
11tmux is a modern analogue of screen. Aug 14, 2010 at 2:21
I don't know about modern, but default key prefix of tmux (Ctrl + b) helps if you're used to bash/emacs keys.– sajithAug 14, 2010 at 4:15
2screen is pretty cool if you want a shared terminal for some reason. Create a screen
screen -S nameand let your other friend connect to it with
screen -x name.– PatrickOct 6, 2010 at 9:23
tmuxinatoris a great combination for fancy setups, while I prefer
screenas a quick and simple solution. Jun 19, 2014 at 15:31
Kto kill the screen session. Answer with
yto confirm the
Really kill this windowquestion.– UserFeb 27, 2017 at 13:36
If you haven't planned ahead and setup
screen, etc. just do the following:
If your process is running in the background: goto #3, else:
Ctrl-Zto suspend foreground process. This will report the job # of the suspended process, for example:
+ Stopped processName
processNameto the background with
bg %1(using whatever the job # is following the
%). This will resume
processNamein the background.
disown PID. Use the
-hflag if you want to maintain ownership until you terminate your current shell.
6Thanks for this! I had a job running and thought I wasn't going to be able to keep it going because I hadn't used
&when I started it. This seems to work great!– MattMar 25, 2012 at 15:42
5This is amazing! I never knew Linux could let you transfer control of active processes like this. I was afraid my battery would die while SSH'ing into my server in the middle of a long running process, and this was the answer for me!– PlutoMay 20, 2014 at 21:05
1Does a disowned process dies if it needs stderr or stdout? Compared to
nohup.– it3xlSep 26, 2021 at 17:12
What you want to use is screen or even better a user-friendly wrapper around screen called byobu.
Screen allows you to run multiple virtual terminal sessions in the same ssh session. A tutorial and help pages are available.
byobu is a wrapper that allows to easily open new screens with a simple function key instead of key combination from ctrl-a. It also shows a status line with all the open virtual terminals which can be named.
Another nice feature is the fact that all your screen can stay up while your ssh connection is disconnected. You just connect again via ssh and call byobu and everything is like before.
At last some screenshots of byobu.
I launched a process on my server within Byobu Terminal without really knowing what it was (I just searched Terminal and clicked on Byobu because I'd never seen it before). I kept using Byobu because it had a colorful status bar at the bottom and I thought it was cool. Today I found myself wanting to access that terminal session remotely through SSH. All I had to do was type "byobu" and it showed that terminal session right away. Really happy I stumbled across byobu!– nickMar 10, 2015 at 20:13
It might be worth noting that
ssh -t lala screen -rxU moo will attach to the moo session on host lala
ssh -t lala screen -S moo will create the moo session on host lala
ssh -t lala screen -S moo quux will create the moo session on host lala and run the program quux, quitting the session on completion.
Old question, strange still nobody advised tmux, which acts as a wrapper for n consoles and keep them open until needed. This allows more control, beside a number of functions tmux has. It's easy to manage it, you just execute tmux, which brings you in its shell, start your looong job, then press ctrl+b followed by d (detach) (
ctrl+b is the "ok google" of tmux, and
d is the command to close without exit from the shell). This actually works if you just close, for example, putty. After dinner, when you connect again, you can reopen tmux with
tmux attach to see your screen exactly as you left. Something I love is splitting pane:
ctrl+b and then press
". To change from one pane to another,
ctrl+b and then press the up/down arrow.
Tmux is a good option available to run your long-running processes in the background.
I have to keep running the long-running processes on a google cloud platform's VM instance/server (with OS: Ubuntu 16.0). Where I have to start SSH terminal and from the terminal, I have to keep the terminal connected to run the process. Now up to this, all is good. But wait if the connection with my SSH terminal is terminated then the long-running processes stop immediately and hence I have to re-run them once again once the ssh terminal is restarted or from a new ssh terminal.
tmux is the good solution to avoid termination of processes that we want to run even after the terminal is closed.
Terminal Multiplexer (
tmux) to start the
- Start the ssh terminal
tmux. It will open a window in the same terminal.
- Run the command to start long-running processes in the tmux session.
Now even if SSH terminal is closed/terminated suddenly tmux session will keep running the started lon-running processes on the instance/server.
If the connection terminated then how to reconnect it to see the processes running in the tmux session in the background:
- reconnect or open new ssh terminal. To see this process(which is kept running in the background) type:
Want to terminate tmux session:
- Stop the process. Then type
(Note that: If we use
tmux detach command: it will exit from tmux session window/terminal without terminating/stopping the tmux sessions)
For more details please refer following article:
You can find a good guide here: Keep Your SSH Session Running when You Disconnect
sudo apt-get install screen
Now you can start a new screen session by just typing screen at the command line. You’ll be shown some information about screen. Hit enter, and you’ll be at a normal prompt.
To disconnect (but leave the session running) Hit Ctrl + A and then Ctrl + D in immediate succession. You will see the message [detached]
To reconnect to an already running session
To reconnect to an existing session, or create a new one if none exists
screen -D -r
To create a new window inside of a running screen session Hit Ctrl + A and then C in immediate succession. You will see a new prompt.
To switch from one screen window to another Hit Ctrl + A and then Ctrl + A in immediate succession.
To list open screen windows Hit Ctrl + A and then W in immediate succession
You can use
<kbd>Ctrl</kbd>to show the names as keyboard keys.– user147505Dec 22, 2016 at 7:41
In 2021 we can also suggest for linux distributions with systemd the use of
systemd-run as a way to detach a process and keep it running after closing ssh login.
One can launch a
command , give it some name like 'background_cmd_service' and turn it into a systemd service. Later inspect status:
systemd-run --unit=background_cmd_service --remain-after-exit command # later on journalctl -b -u background_cmd_service.service systemctl status background_cmd_service.service
When launching the service as regular user, one might need to enable lingering (cf.
enable-linger loginctl option). This is true even with nohup since systemd is cleaning up all services running within the session once the user logs out.
For scripts, or other executables, you can provide the path to the executable like this:
systemd-run --unit=background_cmd_service --remain-after-exit --working-directory=/full/path/ command
You can also stop your service or clear a failed service using the standard
systemctl options like:
systemctl stop background_cmd_service.service
systemctl reset-failed background_cmd_service.service
Many of the pre-2016, but highly voted answers on stack exchange suggesting
command &, and
(command &) don't work since 2016, due to a systemd default change in how it treats user processes after user logout - Details
enable-linger needs root access or some sort of authentication - is there any way to do this without root?– ElenchusFeb 9, 2022 at 13:49
1@Elenchus You can run "loginctl disable-linger|enable-linger" with a regular no root user to set lingering state for the current user running the command. At least this is the default setup on Debian/11. Changing login lingering for other users requires root access.– kalikoFeb 10, 2022 at 15:52
I get a message saying 'Authentication is required to run programs as a non-logged-in user' and then it gives me a list of a few users to authenticate as - the names I recognise are from our IT department, so I thought it might be a root thing. I guess they've changed the default behaviour - their ethos seems to be to disable everything until enough people complain about it. Thanks for the info, anyway– ElenchusFeb 11, 2022 at 2:37
I use NX NoMachine, which is free for me because it's only me. Essentially, it runs an X session on the server which you can connect to and disconnect from over and over. The X session keeps running when you're not connected. Connections can be made from anywhere. You can choose between floating windows or a single window containing a whole desktop (eg a complete Gnome desktop). The client (which you would run on your laptop) can be run on Linux, MacOS, Solaris or Microsoft Windows. In the latter case if you choose floating windows they appear individually on the Windows Taskbar.
I use my Windows XP laptop (which I need for certain Windows-specific hardware I have) as a front end for my two Linux servers using NX Nomachine. I can even print to the printer attached to my Windows laptop from Linux.
If you want to run the process in a non-interactive ssh session (so
screen are out) you can do:
ssh SERVER 'nohup bash -c "echo start; sleep 10; echo finish"'
The process will continue if the ssh session is interrupted but you cannot reconnect to see its output.
ssh SERVER 'nohup bash -c "(echo start; sleep 10; echo finish)|tee -p /tmp/log"'
This will show you the output during the ssh session and if it disconnects
tee -p will continue to write to the
Note: since the session is not interactive you can't use
& to put the job into the background.