(nohup invocation): POSIXLY_CORRECT no longer

affects nohup's behavior.  Input is redirected from /dev/null.
This commit is contained in:
Paul Eggert committed 2005-07-15 21:54:56 +00:00
1 parent 738c09d59c
commit adbbc35f87
1 file changed
+7 -8
+7 -8
View File
@@ -12615,6 +12615,13 @@ out. Synopsis:
nohup @var{command} [@var{arg}]@dots{}
@end example
If standard input is a terminal, it is redirected from
@file{/dev/null} so that terminal sessions do not mistakenly consider
the terminal to be used by the command. This is a @acronym{GNU}
extension; programs intended to be portable to non-@acronym{GNU} hosts
should use @samp{nohup @var{command} [@var{arg}]@dots{} </dev/null}
instead.
@flindex nohup.out
If standard output is a terminal, the command's standard output is appended
to the file @file{nohup.out}; if that cannot be written to, it is appended
@@ -12627,14 +12634,6 @@ regardless of the current umask settings.
If standard error is a terminal, it is redirected to the same file
descriptor as the (possibly-redirected) standard output.
@vindex POSIXLY_CORRECT
If standard input is a terminal, it is closed so that terminal
sessions do not mistakenly consider the terminal to be used by the
command. To avoid glitches in poorly-written programs standard input
is then reopened with an innocuous file descriptor that cannot be read
from. However, these steps are skipped if @env{POSIXLY_CORRECT} is
set since @acronym{POSIX} requires standard input to be left alone.
@command{nohup} does not automatically put the command it runs in the
background; you must do that explicitly, by ending the command line
with an @samp{&}. Also, @command{nohup} does not change the