[Openvas-commits] r3199 - trunk/doc/website

[scm-commit@wald.intevation.org]

Author: lmwangi
Date: 2009-04-27 00:37:29 +0200 (Mon, 27 Apr 2009)
New Revision: 3199

Modified:
   trunk/doc/website/openvas-cr-29.htm4
Log:
fleshing out logging cr

Modified: trunk/doc/website/openvas-cr-29.htm4
===================================================================
--- trunk/doc/website/openvas-cr-29.htm4	2009-04-26 18:59:36 UTC (rev 3198)
+++ trunk/doc/website/openvas-cr-29.htm4	2009-04-26 22:37:29 UTC (rev 3199)
@@ -67,11 +67,19 @@
 debug functions to accomplish this.<br />
 Use of g_log for all logging within OpenVAS.<br />
 <ul>
-<li>Definition of G_LOG_DOMAIN within autoconf to identify library messages</li>
-<li>Use of g_log_set_handler () to route messages to different logfiles depending on the domain and log_level (severity) similar to apache access and error logfiles. Can Probably be done in a dynamic fashion from config files</li>
-<li>Definition of a prepend string in a config file much like PHP's html error prepend string</li>
+<li>Definition of G_LOG_DOMAIN within autoconf/Makefiles to identify library/subsystem message sources</li>
+<li>Use of g_log_set_handler () in openvasd's main() to route messages to different logfiles depending on the domain and log_level (severity) similar to apache access and error logfiles. Can be done in a dynamic fashion by loading parameters from a glib keyfile </li>
+<li>Using glib's IO Channels to handle log output to files</li>
+<li>Definition of a prepend string in a config file much like PHP's html error prepend string based on the following proposal:</li>
+	<ul>
+	<li>%P: PID</li>
+	<li>%{format}t: Format string to format glib's GTimeVal</li>
+	<li>%u: Remote user</li>
+	<li>Use of __LINE__ and __FILE__ in debug messages..?</li>
+	</ul>
 <li>Definition of an append string in a config file much like PHP's html error append string</li>
 <li>Classification of existing log outputs and addition of new ones for debug</li>
+<li>We also have to add "if (!g_thread_supported ()) g_thread_init (NULL);" openvasd's main() to make logging thread safe </li>
 <li>If we have time and manpower, use assert statements to catch bugs we wouldn't know about - Have a look at glib-Warnings-and-Assertions.html in glib's documentation</li>
 </ul>
 </p>
@@ -79,6 +87,7 @@
 <h3>History</h3>
 
 <ul>
+<li> 2009-04-25 Laban Mwangi &lt;lmwangi at penguinlabs.co.ke&gt;:<br/> Adding details based on testing.</li>
 <li> 2009-04-14 Laban Mwangi &lt;lmwangi at penguinlabs.co.ke&gt;:<br/> Integrating with glib logging.</li>
 <li> 2009-04-08 Laban Mwangi &lt;lmwangi at penguinlabs.co.ke&gt;:<br/> Initial text.</li>
 </ul>