Nohup: Difference between revisions
No edit summary |
No edit summary |
||
Line 9: | Line 9: | ||
=Overview= | =Overview= | ||
<tt>nohup</tt> is a POSIX command to ignore the HUP (hangup) signal. The HUP signal is, by convention, the way a terminal warns dependent processes of logout. | <tt>nohup</tt> is a POSIX command to ignore the HUP (hangup) signal. The [[Linux_Signals#SIGHUP_.281.29|HUP signal]] is, by convention, the way a terminal warns dependent processes of logout. | ||
<pre> | <pre> |
Revision as of 18:53, 14 October 2016
External
- nohup on wikipedia http://en.wikipedia.org/wiki/Nohup
Internal
Overview
nohup is a POSIX command to ignore the HUP (hangup) signal. The HUP signal is, by convention, the way a terminal warns dependent processes of logout.
nohup command &
Output that would normally go to the terminal goes to a file called ./nohup.out if it has not already been redirected.
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 be overcome by redirecting all three I/O streams:
{{{ $ nohup ./myprogram > foo.out 2> foo.err < /dev/null & }}}
!!!Solution Used to Background gld Remotely
status to interact with it"
sleep 1
else ... fi
__Referenced by:__\\ [{INSERT com.ecyrd.jspwiki.plugin.ReferringPagesPlugin WHERE max=20, maxwidth=50}]