summaryrefslogtreecommitdiff
path: root/doc/tipideed.html
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2023-10-12 10:17:47 +0000
committerLaurent Bercot <ska@appnovation.com>2023-10-12 10:17:47 +0000
commit3b0a901275e63ca7a0d46a5f58bdc6d1f706ce06 (patch)
tree4cc508d5b23733117e58547c431abb069621ed65 /doc/tipideed.html
parentd9492e8561fe5373b1428c6d7cff4f25e2796a55 (diff)
downloadtipidee-3b0a901275e63ca7a0d46a5f58bdc6d1f706ce06.tar.xz
New logging system; not used yet in tipideed
Signed-off-by: Laurent Bercot <ska@appnovation.com>
Diffstat (limited to 'doc/tipideed.html')
-rw-r--r--doc/tipideed.html41
1 files changed, 35 insertions, 6 deletions
diff --git a/doc/tipideed.html b/doc/tipideed.html
index 8f080bc..977317c 100644
--- a/doc/tipideed.html
+++ b/doc/tipideed.html
@@ -28,7 +28,7 @@ a web server package: it serves files over HTTP.
</div>
<pre>
- tipideed [ -v <em>verbosity</em> ] [ -f <em>cdbfile</em> ] [ -d <em>basedir</em> ] [ -R ] [ -U ]
+ tipideed [ -f <em>cdbfile</em> ] [ -d <em>basedir</em> ] [ -R ] [ -U ]
</pre>
<ul>
@@ -201,11 +201,6 @@ cannot be used by CGI scripts in a portable way.
</div>
<dl>
- <dt> -v <em>verbosity</em> </dt>
- <dd> The level of log verbosity. This is the same as the <tt>global verbosity</tt>
-setting in the <a href="tipidee.conf.html#verbosity">configuration file</a>; an explicit
-command line option overrides any setting present in the configuration file.</dd>
-
<dt> -f <em>file</em> </dt>
<dd> Use <em>file</em> as the compiled configuration database, typically obtained
by running <tt><a href="tipidee-config.html">tipidee-config</a> -o <em>file</em></tt>.
@@ -335,6 +330,40 @@ at all, your documents will most likely be accessible for HTTP/1.0 clients under
<tt>@:80</tt> or <tt>@:443</tt>.
</p>
+<div id="logging">
+<h2> Logging </h2>
+</div>
+
+<ul>
+ <li> tipideed uses stderr for all its logging. All its log lines are prefixed
+with "<tt>tipideed: pid <em>pid</em>: </tt>". </li>
+ <li> The log lines continue with "<tt>fatal: </tt>" for fatal error messages (meaning
+that tipideed exits right after writing the message), or "<tt>warning: </tt>" for
+warnings (meaning that tipideed continues operating after writing the message).
+In normal operation, you should not see any fatal or warning line. </li>
+ <li> In normal operation, tipidee can log informational lines, and the continuing
+prefix is "<tt>info: </tt>". It can potentially log:
+ <ul>
+ <li> One line when it starts (i.e. a client has connected) </li>
+ <li> Up to three lines for every request:
+ <ul>
+ <li> One when the request is received </li>
+ <li> One when a suitable resource is found </li>
+ <li> One when an answer is sent </li>
+ </ul> </li>
+ <li> One line when it exits normally </li>
+ </ul> </li>
+ <li> What informational lines to log is configured via the
+<a href="tipidee.conf.html#log"><tt>log</tt></a> directive in the
+<a href="tipidee.conf.html">configuration file</a>. By default, only
+a minimal request line and an answer line are printed. </li>
+ <li> The log format is designed to be readable by a human, but still
+easily processable by automation. For instance, the regular prefix structure
+makes it easy for <a href="//skarnet.org/software/s6/s6-log.html">s6-log</a>
+to select different lines to send them to various backends for archiving or
+processing. </li>
+</ul>
+
<div id="details">
<h2> Detailed operation </h2>
</div>