Historical implementations of @command{tail} have required that
@var{number} be an integer. However, GNU @command{tail} accepts
an arbitrary floating point number. @xref{Floating point}.
-When @command{tail} uses inotify, this polling-related option is ignored.
+When @command{tail} uses inotify, this polling-related option
+is usually ignored. However, if you also specify @option{--pid=@var{p}},
+@command{tail} checks whether process @var{p} is alive at least
+every @var{number} seconds.
@itemx --pid=@var{pid}
@opindex --pid
fputs (_("\
-s, --sleep-interval=N with -f, sleep for approximately N seconds\n\
(default 1.0) between iterations.\n\
- With inotify, this option is rarely useful.\n\
+ With inotify and --pid=P, check process P at\n\
+ least once every N seconds.\n\
-v, --verbose always output headers giving file names\n\
"), stdout);
fputs (HELP_OPTION_DESCRIPTION, stdout);
evlen += sizeof (struct inotify_event) + 1;
evbuf = xmalloc (evlen);
- /* Wait for inotify events and handle them. Events on directories make sure
- that watched files can be re-added when -F is used.
- This loop sleeps on the `safe_read' call until a new event is notified. */
+ /* Wait for inotify events and handle them. Events on directories
+ ensure that watched files can be re-added when following by name.
+ This loop blocks on the `safe_read' call until a new event is notified.
+ But when --pid=P is specified, tail usually waits via the select. */
while (1)
{
struct File_spec *fspec;