Most of the time you login into remote server via ssh. If you start a shell script or command and you exit (abort remote connection), the process / command will get killed. Sometime job or command takes a long time. If you are not sure when the job will finish, then it is better to leave job running in background. However, if you logout the system, the job will be stopped. What do you do?
nohup command
Answer is simple, use nohup utility which allows to run command./process or shell script that can continue running in the background after you log out from a shell:
nohup Syntax:
nohup command-name &
Where,
- command-name : is name of shell script or command name. You can pass argument to command or a shell script.
- & : nohup does not automatically put the command it runs in the background; you must do that explicitly, by ending the command line with an & symbol.
nohup command examples
1) Login to remote server
$ ssh user@remote.server.com
2) Execute script called pullftp.sh
# nohup pullftp.sh &
Type exit or press CTRL + D exit from remote server.
# exit
3) Find all programs and scripts with setuid bit set on, enter:
# nohup find / -xdev -type f -perm +u=s -print > out.txt &
Type exit or press CTRL + D exit from remote server.
# exit
Please note that nohup does not change the scheduling priority of COMMAND; use nice for that:
# nohup nice -n -5 ls / > out.txt &
As you can see nohup keep processes running after you exit from a shell. Read man page of nohup and nice command for more information. Please note that nohup is almost available on Solaris/BSD/Linux/UNIX variant.
Update:
# 1: As pointed out by Jason you can use at command to queue a job for later execution. For example, you can run pullftp.sh script to queue (one minute) later execution
$ echo "pullftp.sh" | at now + 1 minute
# 2: You can also use screen command for same. Brock pointed out disown shell internal command for same purpose. Here is how you can try it out:
$ pullftp.sh &
$ disown -h
$ exit
According to bash man page:
By default, removes each JOBSPEC argument from the table of active jobs. If the -h option is given, the job is not removed from the table, but is marked so that SIGHUP is not sent to the job if the shell receives a SIGHUP. The -a option, when JOBSPEC is not supplied, means to remove all jobs from the job table; the -r option means to remove only running jobs.
Featured Articles:
- 20 Linux System Monitoring Tools Every SysAdmin Should Know
- 20 Linux Server Hardening Security Tips
- 10 Greatest Open Source Software Of 2009
- My 10 UNIX Command Line Mistakes
- Top 5 Email Client For Linux, Mac OS X, and Windows Users
- Top 20 OpenSSH Server Best Security Practices
- Top 10 Open Source Web-Based Project Management Software
- Top 5 Linux Video Editor Software
- Email this to a friend
- Download PDF version
- Printable version
- Comment RSS feed
- Last Updated: Oct/22/2008



{ 18 comments… read them below or add one }
You forget the other easy way to do the same: the ‘at’ command!
> echo “pullftp.sh” | at now + 1 minute
Then logout. After the job completes, you’ll even get an email message with the contents of stdout/stderr.
Jason thanks for pointing out at command :) appreciate your post.
I have screen installed on all servers. Not only detaching (nohup), but also opening new consoles etc.
Heh, my bad.
Stoyan thanks for reminding us about screen manager :) I will update post tomorrow (it is late night now) with screen utility.
Screen is good, but there’s also “disown” in bash, which leaves jobs running even if you log out.
Brock, seems good choice, thanks
Thank you. I’ve been searching for this. I knew this kind a functionality should exist. Often i had this issue when ever I’m connecting from home to my office-server.
BR :)
Hi everybody.
I am working as sys admin on linux and now i want to learn a programming lanuage can anybody suggest which one i should go for. Which can help me both at admin work and with small app programs.
regards
anil
Screen is definitely the best way to do this.
You can run commands and then detach the screen, Ctrl+a+d and leave the command running
Thanks. Excellent for those lengthy commits!
I used nohup as follows… nohup ./command &. Did I make a mistake in putting the “./” in front of the command when executing it?
./ means run command from current directory. Do you have command in current dir?
Thanks for the reply. Yes command is in current directory but nohup log lists several complaints about not being able to find various files. Also, when executing, I was expecting to be returned to the command prompt which I was not.
I just checked with my Unix admin who thinks that it does not matter whether you include the ./ in the nohup string. Also, If I hit return during the process I get my prompt back and can run a monitoring script.
What kind of error you get in log files? When you get prompt back what do you see with ps and jobs command?
Hi and thanks for the reply. I am seeing error messages that files cannot be found that I know are present in a different folder (where it should be looking). That is what concerned me that I might have forced the process to look only in it’s current directory with “./”. When I get the prompt back I can ps and see the job running.
I have the situation…
I did ssh to the remote server. Run the yum -y update command without nohup!
The updating run for a while and I want to log out off the remote server…and I want yum still run even I log out..
How can I use ‘nohup’ without canceling my update !
thanks for any suggestions !!
I found these two methods googling:
Method 1:
- start the process from console
- send it to background CTRL + Z
- then disown -a
Method 2:
nohup command