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/.

Neels Hofmeyr nhofmeyr at sysmocom.de
Wed Jul 25 14:33:22 UTC 2018


On Wed, Jul 25, 2018 at 11:16:46AM +0200, Pau Espin Pedrol wrote:
> 2- Modification: "logging level all <loglevel>" sets the loglevel foreach
> category, not the target loglevel (aka the default loglevel).
> 3- Modification: "logging level unset <loglevel>" is renamed to "logging
> level default <loglevel>"

I find both 'logging level unset <level>' and 'logging level default <level>'
confusing. Did you mean to say '<category>'?

> For num.4, we could actually use "logging level all unset", which makes
> perfectly sense and matches with expectations.

IMHO "level unset" doesn't spark a meaningful image. Sounds like "allow any
level", or next best meaning is "back to hardcoded defaults".

~N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20180725/6979149a/attachment.bin>


More information about the OpenBSC mailing list