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
Thu Aug 30 19:23:10 UTC 2018


Hi Neels,

On Thu, Aug 30, 2018 at 04:05:45PM +0200, Neels Hofmeyr wrote:
> With a bit of time passed, I am revisiting this.
> 
> It seems that my plan to have a per-subsystem configurable default log level as
> well as a per-subsystem configurable elevated/silenced log level is pretty much
> off the table.
> 
> So then, for me that means it opens the door to accept Pau's patch.

At this point, I am sorry to say the topic has somehow become somewhat of a
"red flag" to me.  So I'll hereby bestow you with the title of
"Osmocom Supreme Chief Logging Officer" and you get all the freedom to decide
how you'd like to change it, as you see fit.

My rough outline is:
* try to handle existing config files in a useful way, without obvious breakage
* make sure all documentation is updated at the very same time as the change is
  merged, so that user manuals / vty reference / wiki / etc. are correct.

This is without bitterness, don't get me wrong.  I just don't feel like I
can come to a good conclusion here, and hence I delegate it and make it your
problem :P

Regards,
	Harald
-- 
- 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