Files
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
automated terminal push
2025-06-04 11:50:30 -04:00

19 lines
630 B
Markdown
Executable File

# 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
```