Dan Winship 1d42962e7f logging: fix "nmcli gen log level FOO" ... The change to per-domain log levels means that when setting just the level, we need to re-set the log level for each domain (since it's the "logging" bit array that actually determines what gets logged). nm_logging_setup() was dealing correctly with domains=NULL, but not domains="" (which is what happens when it is invoked with only a level via D-Bus), so doing "nmcli gen log level DEBUG" would change the "default" log level, but leave all of the domains still at their previous level: danw@laptop:NetworkManager> nmcli g log LEVEL DOMAINS INFO PLATFORM,RFKILL,ETHER,WIFI,BT,MB,DHCP4,DHCP6,PPP,IP4,IP6... danw@laptop:NetworkManager> nmcli g log level DEBUG danw@laptop:NetworkManager> nmcli g log LEVEL DOMAINS DEBUG PLATFORM:INFO,RFKILL:INFO,ETHER:INFO,WIFI:INFO,BT:INFO...		2014-01-22 09:48:42 -05:00
..
nm-logging.c	logging: fix "nmcli gen log level FOO"	2014-01-22 09:48:42 -05:00
nm-logging.h	core: fix leak in impl_manager_get_logging	2013-12-20 10:04:11 -05:00