From 5e8ad5a5773b5d2e2c1d266e6287263b3ea225a5 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Sat, 31 Jul 1999 09:03:43 +0000 Subject: *** empty log message *** --- doc/textutils.texi | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) (limited to 'doc') diff --git a/doc/textutils.texi b/doc/textutils.texi index a7d0c1fa8..e4dbcef9a 100644 --- a/doc/textutils.texi +++ b/doc/textutils.texi @@ -1529,14 +1529,13 @@ changed size. @opindex --pid When following by name or by descriptor, you may specify the process ID, @var{pid}, of the sole writer of all @var{file} arguments. Then, shortly -after that process terminates, tail will also terminate. This will work -properly only if the tailing process and the writer are on the same -machine and the tailing process is able to send signals to the writing -process (@code{tail} does not actually send any signal). For example, -to save the output of a build in a file and to watch the file grow, if -you invoke @code{make} and @code{tail} like this then the tail process -will stop when your build completes. Without this option, you would -have had to kill the @code{tail -f} process yourself. +after that process terminates, tail will also terminate. This will +work properly only if the writer and the tailing process are running on +the same machine. For example, to save the output of a build in a file +and to watch the file grow, if you invoke @code{make} and @code{tail} +like this then the tail process will stop when your build completes. +Without this option, you would have had to kill the @code{tail -f} +process yourself. @example $ make >& makerr & tail --pid=$! -f makerr @end example -- cgit v1.2.3-54-g00ecf