From 54b6467013bfbdb3ee606961c02fbff1271ca582 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Fri, 19 Sep 2014 15:01:58 +0000 Subject: initial commit --- doc/s6-logwatch.html | 72 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 72 insertions(+) create mode 100644 doc/s6-logwatch.html (limited to 'doc/s6-logwatch.html') diff --git a/doc/s6-logwatch.html b/doc/s6-logwatch.html new file mode 100644 index 0000000..5075d83 --- /dev/null +++ b/doc/s6-logwatch.html @@ -0,0 +1,72 @@ + + + + + s6-linux-utils: the s6-logwatch program + + + + + + +

+s6-linux-utils
+Software
+skarnet.org +

+ +

The `s6-logwatch` program

+ +

+s6-logwatch watches the current file of a logdir, printing it +in real time. +

+ +

Interface

+ +

+     s6-logwatch [ -m buflen ] logdir
+

+ +

s6-logwatch prints logdir/current and watches +the file.
logdir must be managed by a +s6-log instance.
When new logs are appended to the current file, s6-logwatch prints +them in real-time to stdout.
When a rotation happens, s6-logwatch notices, and keeps watching the +new current file.
s6-logwatch runs forever until killed.�

+ +

Options

+ +

-m buflen : accumulate at most buflen +bytes into the stdout buffer before flushing it. By default, buflen is +4000.

+ +

Bugs

+ +

s6-logwatch is not entirely reliable because there is an unavoidable +race condition when a rotation occurs; it's a hack for humans to keep reading +logs across rotations, not a tool to be used in safe programming. When the +race condition is triggered, s6-logwatch will be unable to understand what +state logdir is in and will exit 101 with an error message.
Specific support in the logger program would be needed to avoid this +race condition; it would significantly bloat the logger program, so it has +not been deemed useful.

+ +

Notes

+ +

s6-logwatch is Linux-specific because it uses the +inotify interface.

+ + + -- cgit v1.2.3

The s6-logwatch program

Interface

Options

Bugs

Notes

The `s6-logwatch` program