Changes between Version 4 and Version 5 of Logging

Timestamp:

2012-10-05T08:35:01Z (13 years ago)

Author:

Vojtech Horky

Comment:

Write section about changing log level at boot-time

Logging

@@ -34 +34 @@
 || `LVL_DEBUG2` || More detailed debugging message. ||
 
+By default, messages with level `LVL_NOTE` and above (i. e. warning and errors) are printed. To see the debugging messages, the user has to enable them: see below how to increase the verbosity level at boot-time and at run-time.
+
 
 == Going through existing logs ==
@@ -50 +52 @@
 
 
-== Changing reported level at boot time ==
+== Changing reported level at boot-time ==
 
 The following currently works only for GRUB-based platforms.
 
-TODO - logger arguments
+To change the default reporting level, simply add its name (e. g. `fatal` or `debug2`) after the `logger` module load in the GRUB.
+
+'''Example (making default reporting level less verbose)''': append the word `warn` to the logger module line once the GRUB menu appears (use `e` to enter the edit mode).
+{{{
+#!html
+<div class="code"><pre>module /boot/logger /boot/logger <b>warn</b></pre></div>
+}}}
+Then use `F10` to boot HelenOS.
+
+It is also possible to change reporting level of an individual log. Simply write the log name and append to it the desired level. This can be repeated for more logs.
+
+'''Example (making tester very verbose)''': change the logger line to the following.
+{{{
+#!html
+<div class="code"><pre>module /boot/logger /boot/logger <b>tester=debug2</b></pre></div>
+}}}
+
+Both possibilities can be combined. For example, it is possible to set the default reporting level to errors only and only make several (problematic) drivers more verbose.
+
 
 == Changing reported level at run-time ==