From ad2dee7ffa6ebd7a5c68ffb99d02aac4fa3e993e Mon Sep 17 00:00:00 2001
From: Laurent Bercot <ska-skaware@skarnet.org>
Date: Wed, 25 Oct 2017 15:59:33 +0000
Subject:  Document s6-log's -l option

---
 doc/s6-log.html | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/doc/s6-log.html b/doc/s6-log.html
index 0bb9916..4f6dcc8 100644
--- a/doc/s6-log.html
+++ b/doc/s6-log.html
@@ -27,7 +27,7 @@ with full POSIX regular expression support.
 <h2> Interface </h2>
 
 <pre>
-     s6-log [ -q | -v ] [ -b ] [ -p ] [ -t ] [ -e ] <em>logging script</em>
+     s6-log [ -q | -v ] [ -b ] [ -p ] [ -t ] [ -e ] [ -l linelimit ] <em>logging script</em>
 </pre>
 
 <p>
@@ -66,6 +66,13 @@ Currently supported verbosity levels:
    <li> 0: only write alerts and fatal errors </li>
    <li> 1: write alerts, warnings and fatal errors </li>
   </ul> </li>
+ <li> <tt>-l&nbsp;<em>linelimit</em></tt>&nbsp;: if a log line is longer than
+<em>linelimit</em> bytes, cut it in two by inserting a newline. The newline
+may appear anywhere after <em>linelimit</em> or more bytes. <em>linelimit</em>
+cannot be lesser than 48. Using this option ensures that an ill-formatted log
+stream will not make s6-log uncontrollably eat memory by trying to read and
+process an extremely long line in one go. The default is no cap on line
+length. </li>
 </ul>
 
 <h2> Logdirs </h2>
-- 
cgit v1.2.3