+2007-04-28 Paul Eggert <eggert@cs.ucla.edu>
+
+ * src/nohup.c (usage): Describe how standard input and output
+ are redirected.
+
2007-04-25 Jim Meyering <jim@meyering.net>
* src/du.c (usage): Clarify description of --dereference-args (-D).
+2007-04-28 Paul Eggert <eggert@cs.ucla.edu>
+
+ * coreutils.texi (nohup invocation): Add advice about saving
+ output to a file.
+
2007-04-16 Jim Meyering <jim@meyering.net>
* coreutils.texi (cut invocation): Adjust synopsis to show that an
is instead appended to the file @file{nohup.out} or
@file{$HOME/nohup.out} as above.
+To capture the command's output to a file other than @file{nohup.out}
+you can redirect it. For example, to capture the output of
+@command{make}:
+
+@example
+nohup make > make.log
+@end example
+
@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 alter the
strverscmp.c
strverscmp.h
sys
+sys_socket.h
+sys_socket_.h
+sys_stat.h
+sys_stat_.h
sys_time.h
sys_time_.h
t-fpending
strverscmp.c
strverscmp.h
sys
+sys_socket.h
+sys_socket_.h
+sys_stat.h
+sys_stat_.h
sys_time.h
sys_time_.h
t-fpending
"), stdout);
fputs (HELP_OPTION_DESCRIPTION, stdout);
fputs (VERSION_OPTION_DESCRIPTION, stdout);
+ printf (_("\n\
+If standard input is a terminal, redirect it from /dev/null.\n\
+If standard output is a terminal, append output to `nohup.out' if possible,\n\
+`$HOME/nohup.out' otherwise.\n\
+If standard error is a terminal, redirect it to standard output.\n\
+To save output to FILE, use `%s COMMAND > FILE'.\n"),
+ program_name);
printf (USAGE_BUILTIN_WARNING, PROGRAM_NAME);
emit_bug_reporting_address ();
}