nohup for persistent processes in Linux CLI - Commands & Configuration

Introduction

Sometimes you want a program to keep running even after you close the terminal. The nohup command helps you do this by ignoring the hangup signal, so your process keeps working in the background.

When you start a long script on a remote server and want it to keep running after you disconnect.

When you launch a backup job that takes hours and you don't want to keep the terminal open.

When running a server or service manually and want it to stay alive after logout.

When testing a command that might take a long time and you want to avoid accidental termination.

When you want to save the output of a command to a file while it runs in the background.

Commands

This command runs the 'sleep 60' command in the background and uses nohup to keep it running even if the terminal closes.

Terminal

nohup sleep 60 &

Expected Output

nohup: ignoring input and appending output to 'nohup.out'

[1] 12345

This command checks if the 'sleep' process is still running after starting it with nohup.

Terminal

ps -ef | grep sleep

Expected Output

user     12345  6789  0 12:00 pts/0    00:00:00 sleep 60

user     12346  1234  0 12:00 pts/0    00:00:00 grep sleep

This command shows the output saved by nohup. Since 'sleep' produces no output, the file will be empty or not created.

Terminal

cat nohup.out

Expected Output

No output (command runs silently)

Key Concept

If you remember nothing else from this pattern, remember: nohup lets a process keep running after you close the terminal by ignoring hangup signals.

Common Mistakes

Running a command with nohup but forgetting to add '&' to run it in the background.

The command will run but the terminal will be blocked until it finishes, defeating the purpose of nohup for persistent background processes.

Always add '&' at the end to run the command in the background, like 'nohup command &'.

Not checking the nohup.out file for output or errors.

You might miss important messages or errors because nohup redirects output to nohup.out by default.

Check the nohup.out file or redirect output explicitly to a file you choose.

Summary

Use 'nohup command &' to run a command that keeps running after terminal closes.

Check running processes with 'ps -ef | grep command' to confirm it's still active.

Look at 'nohup.out' for any output or errors the command produces.

Practice

1. What is the main purpose of using nohup in Linux command line?

easy

A. To speed up the execution of a command

B. To stop a running process immediately

C. To display the output of a command in color

D. To run a command that keeps running after logout or terminal closes

Solution

1. Step 1: Understand the function of nohup

   nohup stands for 'no hang up' and is used to run commands that continue running even after the user logs out or the terminal closes.

2. Step 2: Compare options with this definition

   Only "To run a command that keeps running after logout or terminal closes" matches this purpose. The other options describe unrelated functions.

3. Final Answer:

   To run a command that keeps running after logout or terminal closes -> Option D

4. Quick Check:

   nohup = persistent command run [OK]

Hint: Remember nohup means 'no hang up' to keep process alive [OK]

Common Mistakes:

• Thinking nohup speeds up commands
• Confusing nohup with output coloring
• Assuming nohup stops processes

2. Which of the following is the correct syntax to run my_script.sh persistently in the background using nohup?

easy

A. nohup my_script.sh &

B. nohup & my_script.sh

C. my_script.sh nohup &

D. nohup my_script.sh

Solution

1. Step 1: Recall the correct nohup syntax

   The correct way is to write nohup command & to run the command persistently in the background.

2. Step 2: Check each option

   nohup my_script.sh & matches the correct syntax. nohup & my_script.sh places & before the command incorrectly. my_script.sh nohup & misplaces nohup. nohup my_script.sh runs nohup but not in background.

3. Final Answer:

   nohup my_script.sh & -> Option A

4. Quick Check:

   nohup + command + & = correct syntax [OK]

Hint: Use nohup command & to run in background [OK]

Common Mistakes:

• Placing & before the command
• Omitting & to run in background
• Misplacing nohup after the command

3. What will be the output file created when you run nohup sleep 60 & without redirecting output?

medium

A. No file is created

B. nohup.out

C. output.txt

D. sleep.log

Solution

1. Step 1: Understand nohup default output behavior

   If no output redirection is given, nohup writes stdout and stderr to a file named nohup.out in the current directory.

2. Step 2: Match this with options

   Only nohup.out matches the default output file. Others are incorrect or no file.

3. Final Answer:

   nohup.out -> Option B

4. Quick Check:

   Default nohup output file = nohup.out [OK]

Hint: Default nohup output file is nohup.out if not redirected [OK]

Common Mistakes:

• Assuming no file is created
• Thinking output goes to sleep.log
• Confusing output.txt as default

4. You run nohup my_script.sh & but the process stops after you logout. What is the most likely reason?

medium

A. You did not redirect output, causing terminal hangup

B. You forgot to add & to run in background

C. You ran the command without nohup

D. You closed the terminal before the command started

Solution

1. Step 1: Understand nohup and output redirection

   Without redirecting output, nohup writes to nohup.out, but if permissions or disk issues prevent this, the process may stop on logout.

2. Step 2: Analyze options

   You did not redirect output, causing terminal hangup correctly points to output redirection issues causing hangup. You forgot to add & to run in background is wrong because & was added. You ran the command without nohup is wrong because nohup was used. You closed the terminal before the command started is unlikely as process starts immediately.

3. Final Answer:

   You did not redirect output, causing terminal hangup -> Option A

4. Quick Check:

   Output redirection needed to avoid hangup [OK]

Hint: Always redirect output to avoid hangup with nohup [OK]

Common Mistakes:

• Ignoring output redirection importance
• Assuming & alone keeps process alive
• Thinking nohup always works without output file

5. You want to run backup.sh persistently, save all output to backup.log, and avoid terminal clutter. Which command should you use?

hard

A. ./backup.sh > backup.log 2>&1 &

B. nohup ./backup.sh & > backup.log 2>&1

C. nohup ./backup.sh > backup.log 2>&1 &

D. nohup ./backup.sh 2>&1 > backup.log &

Solution

1. Step 1: Understand output redirection with nohup

   To save both standard output and errors to a file, use command > file 2>&1. The ampersand & runs the command in background.

2. Step 2: Check each option's correctness

   nohup ./backup.sh > backup.log 2>&1 & correctly places redirection before &. nohup ./backup.sh & > backup.log 2>&1 misplaces & before redirection. ./backup.sh > backup.log 2>&1 & lacks nohup. nohup ./backup.sh 2>&1 > backup.log & reverses redirection order, which is incorrect.

3. Final Answer:

   nohup ./backup.sh > backup.log 2>&1 & -> Option C

4. Quick Check:

   nohup + redirect stdout/stderr + & = correct [OK]

Hint: Redirect output before & to save logs with nohup [OK]

Common Mistakes:

• Placing & before output redirection
• Forgetting nohup for persistence
• Reversing stderr and stdout redirection order