You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The sss tools should set their debug level (and thus probably parse arguments) before they proceed to initializing etc. The debug_level variable which controls if the DEBUG messages should be printed is set to 0 (default) prior to parsing arguments, so our DEBUG messages which use debug_level >= 1 wouldn't be printed.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/75
The sss tools should set their debug level (and thus probably parse arguments) before they proceed to initializing etc. The debug_level variable which controls if the DEBUG messages should be printed is set to 0 (default) prior to parsing arguments, so our DEBUG messages which use debug_level >= 1 wouldn't be printed.
Comments
Comment from jhrozek at 2009-08-04 16:12:24
Fields changed
status: new => assigned
Comment from sgallagh at 2009-08-24 17:23:14
Fields changed
milestone: SSSD 0.5.0 => SSSD 0.6.0
Comment from jhrozek at 2009-09-21 16:49:48
Fixed with db329e0
doc: => 0
docupdated: => 0
fixedin: => 0.6.0
resolution: => fixed
status: assigned => closed
tests: => 0
testsupdated: => 0
Comment from dpal at 2012-01-19 02:16:15
Fields changed
rhbz: => 0
Comment from jhrozek at 2017-02-24 15:06:12
Metadata Update from @jhrozek:
The text was updated successfully, but these errors were encountered: