The magic behaviour of 'logging level all LEVEL'

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Harald Welte laforge at gnumonks.org
Mon Jul 30 18:43:05 UTC 2018


On Wed, Jul 25, 2018 at 11:16:46AM +0200, Pau Espin Pedrol wrote:
> So, after your comments and thinking about it, here's my proposal:
> 1- Take my current patchset
> 2- Modification: "logging level all <loglevel>" sets the loglevel foreach
> category, not the target loglevel (aka the default loglevel).

I think the "target loglevel" should/could be abandoned completely.

> 3- Modification: "logging level unset <loglevel>" is renamed to "logging
> level default <loglevel>"

IMHO it should be "logging level SUBSYSTEM unset" or "logging level
SUBSYSTEM default" which would then revert back to the compiled-in level
for that particular subsystem?

I understand you can un-set or fall-back to the compiled-in default
of a given sub-system.  But how can you un-set a given *level* ?!?

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



More information about the OpenBSC mailing list