On Mon, Nov 19, 2012 at 03:13:12PM +0100, Michal Židek wrote:
On 11/19/2012 02:38 PM, Simo Sorce wrote:
>On Mon, 2012-11-19 at 14:13 +0100, Michal Židek wrote:
>>SSSDBG_CRITICAL_FAILURE or SSSDBG_FATAL_FAILURE
>
>It seem that you are expanding the set of errors printed when no debug
>level is set.
>Before it was just the old level 0, now it's the old level 0 and 1.
>Why ?
>
>Simo.
>
No. When global variable debug_level was set to SSSDBG_UNRESOLVED
(this is temporary state) we printed no debug messages. This caused
some information to be lost during initialization when running as
daemon (not with -i). So I decided to print both fatal and critical
messages during this temporary state (originally I was thinking
about printing everything during this state, but that was too
verbose).
Thanks
Michal
I think this is fine. I tested Michal's patch, with working
configuration, nothing is printed which is OK, with broken configuration
you get the error messages.
debug_level setting is also honored.
Ack