'\" t .\" ** The above line should force tbl to be a preprocessor ** .\" Man page for inotail .\" .\" Copyright (c) 2006 Tobias Klauser .\" .\" You may distribute under the terms of the GNU General Public .\" License as specified in the file COPYING that comes with .\" inotail. .pc .TH INOTAIL 1 "2006-08-13" "" "Inotify enhanced tail" .SH NAME inotail \- A fast and light version of tail using inotify .SH SYNOPSIS .B inotail [OPTION]... [FILE]... .SH DESCRIPTION .B inotail is a drop-in replacement for the 'tail' program found in the base installation of every Linux/UNIX system. It makes use of the inotify infrastructure in recent versions of the Linux kernel to speed up tailing files in the follow mode (the '\-f' option). Currently inotail is not fully compatible to neither POSIX or GNU tail but might be in the future. \fINote:\fR inotail will not work on systems running kernels without Inotify. To enable Inotify , please set CONFIG_INOTIFY=y in your kernel configuration and recompile it. .SH OPTIONS .TP .B \-c \fIN\fR output the last N bytes .TP .B \-f keep the file(s) open and print appended data as the file grows .TP .B \-n \fIN\fR output the last N lines (default: 10) .TP .B \-v print headers with file names .TP .B \-h show help and exit .TP .B \-V show inotail version and exit .SH AUTHOR .PP Written by Tobias Klauser .SH SEE ALSO .PP .BR tail(1), .BR inotify(7) ext plumbingsTobias Klauser
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSteven Rostedt (VMware) <rostedt@goodmis.org>2017-01-30 19:27:10 -0500
committerSteven Rostedt (VMware) <rostedt@goodmis.org>2017-01-31 09:13:49 -0500
commit79c6f448c8b79c321e4a1f31f98194e4f6b6cae7 (patch)
tree370efda701f03cccf21e02bb1fdd3b852547d75c /include/uapi/misc
parent0c744ea4f77d72b3dcebb7a8f2684633ec79be88 (diff)
tracing: Fix hwlat kthread migration
The hwlat tracer creates a kernel thread at start of the tracer. It is pinned to a single CPU and will move to the next CPU after each period of running. If the user modifies the migration thread's affinity, it will not change after that happens. The original code created the thread at the first instance it was called, but later was changed to destroy the thread after the tracer was finished, and would not be created until the next instance of the tracer was established. The code that initialized the affinity was only called on the initial instantiation of the tracer. After that, it was not initialized, and the previous affinity did not match the current newly created one, making it appear that the user modified the thread's affinity when it did not, and the thread failed to migrate again. Cc: stable@vger.kernel.org Fixes: 0330f7aa8ee6 ("tracing: Have hwlat trace migrate across tracing_cpumask CPUs") Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'include/uapi/misc')