learn/docker.softwareshinobi.com
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Files
f1997cab0fc03203486e9c9c91a7787a8e4c775e
docker.softwareshinobi.com/docs/Linux-Commands/Process-Management/093-the-nohup-command.md
Software Shinobi f1997cab0f
All checks were successful
code.softwareshinobi.com-learn/docker.softwareshinobi.com/pipeline/head This commit looks good
Details
automated terminal push
2025-06-04 11:50:30 -04:00

630 B
Executable File
Raw Blame History

The nohup command

When a shell exits (maybe while logging out of an SSH session), the HUP ('hang up') signal is send to all of its child processes, causing them to terminate. If you require a long-running process to continue after exiting shell, you'll need the nohup command. Prefixing any command with nohup causes the command to become immune to HUP signals. Additionally, STDIN is being ignored and all output gets redirected to local file ./nohup.out.

Examples:

  1. Applying nohup to a long-running debian upgrade:
nohup apt-get -y upgrade

Syntax:

nohup COMMAND [ARG]...
nohup OPTION