Building Cloud Expertise with centron - Our Tutorials

Whether you are a beginner or an experienced professional, our practical tutorials provide you with the knowledge you need to make the most of our cloud services.

Nohup Command in Linux

When exiting the shell of a Linux System, all running processes are usually terminated or hang up. So what do you do If you still want to keep the processes running even exiting the shell/terminal? This is where the nohup command comes in.

Nohup Command

Nohup, short for no hang up is a command in Linux systems that keep processes running even after exiting the shell or terminal. Nohup prevents the processes or jobs from receiving the SIGHUP (Signal Hang UP) signal. This is a signal that is sent to a process upon closing or exiting the terminal. In this guide, we take a look at the nohup command and demonstrate how it can be used.

Nohup Command Syntax

Nohup command syntax is as follows;


Let’s see how the command comes into play

Checking the version of Nohup

You can begin by checking the version of Nohup using the syntax below


Starting a process using Nohup

If you want to keep your processes/jobs running, precede the command with nohup as shown below. The jobs will still continue running in the shell and will not get killed upon exiting the shell or terminal.


From the output above, the output of the command has been saved to nohup.out to verify this run,


Additionally, you can opt to redirect the output to a different file as shown

nohup ./ > output.txt

Once again, to view the file run


To redirect to a file and to standard error and output use the > filename 2>&1 attribute as shown

nohup ./ > myoutput.txt 2>&1


Starting a process in the background using Nohup

To start a process in the background use the & symbol at the end of the command. In this example, we are pinging and sending it to the background.


To check the process when resuming the shell use the pgrep command as shown


If you want to stop or kill the running process, use the kill command followed by the process ID as shown



  • All processes that are run using the nohup command will ignore the SIGHUP signal even upon exiting the shell.
  • Once a job is started or executed using the nohup command, stdin will not be available to the user.
  • By default, the nohup.out is used as the default file for stdout and stderr.

Start Your Cloud Journey Today with Our Free Trial!

Dive into the world of cloud computing with our exclusive free trial offer. Experience the power, flexibility, and scalability of our cloud solutions firsthand.

Try for free!