[Olsr-dev] DebugLevel that is actually zero

Henning Rogge (spam-protected)
Tue Jul 17 18:34:05 CEST 2012

I think we would have to do even more to make OLSRd shut up... because
some error messages are directly channeled to the syslog... and I
think some are just printed without looking at the debug_level.


On Tue, Jul 17, 2012 at 6:30 PM, Hans-Christoph Steiner
<(spam-protected)> wrote:
> I can't recall seeing a debug level range from -1 to 9 in another app.
> I think debug level 0 is pretty widely understood to mean no messages,
> so IMHO I think the best solution would be to change the messages that
> are posting to level 0.
> If that's not feasible then perhaps the absence of "-d " on the command
> line would mean no messages.  Then there could be "Debug yes/no" in
> olsrd.conf to control whether there are messages or not.
> .hc
> On 07/14/2012 03:12 AM, Henning Rogge wrote:
>> There are some plugins and OS specific parts that seem to use level 0
>> for error output.
>> Easiest fix would be allowing -1 as a debug level, because its stored
>> as an "int" anyways internally.
>> Henning
>> On Fri, Jul 13, 2012 at 4:49 PM, Hans-Christoph Steiner
>> <(spam-protected)> wrote:
>>> One thing that would be very useful is a way to really turn off all
>>> debug messages.  The current "DebugLevel 0" still outputs quite a bit of
>>> stuff.
>>> Is there a way to actually get zero debug messages, like no output to
>>> stdout and stderr at all?  If not, I think it would be good to make
>>> "DebugLevel 0" actually output zero.
>>> .hc
>>> --
>>> Olsr-dev mailing list
>>> (spam-protected)
>>> https://lists.olsr.org/mailman/listinfo/olsr-dev

Steven Hawkings about cosmic inflation: "An increase of billions of
billions of percent in a tiny fraction of a second. Of course, that
was before the present government."

More information about the Olsr-dev mailing list