to much syslogging by default
Pavel Reichl
preichl at redhat.com
Tue Jan 27 12:13:03 EST 2015
On 01/27/2015 05:38 PM, Dan White wrote:
> On 01/27/15 17:28 +0100, Pavel Reichl wrote:
>> Hello,
>>
>> while authenticating SASL fills syslog with lines containing
>> following strings:
>>
>> GSSAPI client step 1
>> GSSAPI client step 1
>> GSSAPI client step 1
>> GSSAPI client step 2
>>
>> I don't think this should be printed at default debug level.
>>
>> Would it be possible to change priority of this messages to not be
>> printed by default?
>>
>> I also tried to work around this problem by creating our own log
>> callback but it seems to be ignored as logging is called with NULL
>> context, so no callbacks are searched...if I read the code correctly.
>>
>> params->utils->log(NULL, SASL_LOG_DEBUG, "GSSAPI client step %d",
>> text->state);
>
> What is your configured log_level (if any), and what log level are you
> logging at in your syslog config?
>
Hello Dan,
I'm not aware the we configure log_level, but if you give me a hint what
to grep for I'll check it.
Actually we are using journal, but it seems that the level is 7.
More information about the Cyrus-sasl
mailing list