用戶:dukeAnt/Fg (Unix)

nohup 是一個POSIX命令，用於忽略HUP（掛斷）信號。

如果沒有指定輸出文件，正常情況下輸出到終端的輸出都被重定向到一個名為nohup.out的文件中。

用法

下方的第一個命令，用來在後台啟動程序abcd，而隨後的登出操作不會終止程序的執行。

$ nohup abcd &
$ exit

Note that these methods prevent the process from being sent a 'stop' signal on logout, but if input/output is being received for these standard I/O files (stdin, stdout, or stderr), they will still hang the terminal. See Overcoming hanging, below.

nohup is often used in combination with the nice command to run processes on a lower priority.

$ nohup nice abcd &

Existing jobs, processes

Some shells (e.g. bash) provide a shell builtin that may be used to prevent SIGHUP being sent or propagated to existing jobs, even if they were not started with nohup. In bash, this can be obtained by using disown -h job; using the same builtin without arguments removes the job from the job table, which also implies that the job will not receive the signal. Before using disown on an active job, it should be stopped by Ctrl-Z, and continued in the background by the bg command. Another relevant bash option is shopt huponexit, which automatically sends the HUP signal to jobs when the shell is exiting normally.

The AIX and Solaris versions of nohup have a -p option that modifies a running process to ignore future SIGHUP signals. Unlike the above-described disown builtin of bash, nohup -p accepts process IDs.

Overcoming hanging

Note that nohupping backgrounded jobs is typically used to avoid terminating them when logging off from a remote SSH session. A different issue that often arises in this situation is that ssh is refusing to log off ("hangs"), since it refuses to lose any data from/to the background job(s). This problem can also be overcome by redirecting all three I/O streams:

$ nohup ./myprogram > foo.out 2> foo.err < /dev/null &

Also note that a closing SSH session does not always send a HUP signal to depending processes. Among others, this depends on whether a pseudo-terminal was allocated or not.

Alternatives

• The screen or tmux command can also detach a process from the current shell. It allows one to reattach to the process later on.

e.g. the following call will run somescript.sh detached from SIGHUP and in the background:

 $ screen -A -m -d -S somename ./somescript.sh &

• The disown command is used to remove jobs from the job table, or to mark jobs so that a SIGHUP signal is not sent

External links

• nohup from Solaris's man pages