silencing rpc.gssd

[Kevin Coffman]

On Wed, Feb 27, 2008 at 3:53 AM, Timo Aaltonen <tjaalton at cc.hut.fi> wrote:
>
>         Hi!
>
>    I've probably asked this before, but there still doesn't seem to be an
>  easy way to make rpc.gssd less verbose when the user ticket has expired
>  and logs start filling up with "Failed to write error downcall" messages?
>  I get those ~2000 per _second_ (likely due to some broken app like
>  tracker..), so my 9GB /var gets filled in 6h.
>
>  Feb 27 03:05:07 deckard rpc.gssd[6403]: WARNING: Failed to create krb5
>  context for user with uid xxxxx for server foo
>  Feb 27 03:05:07 deckard rpc.gssd[6403]: Failed to write error downcall!
>  Feb 27 03:05:07 deckard rpc.gssd[6403]: ERROR: GSS-API: error in
>  gss_acquire_cred(): The referenced credential has expired - No error
>
>  I guess it's simple to just patch do_error_downcall to use verbosity level
>  1 to get rid of the second message, but how to silence the last one which
>  originates from the krb5 library(?) ? If that was possible, then syslogd
>  would be able to bundle the WARNING messages and prevent logs getting
>  filled with crap.

Hi Timo,

Actually that last message is produced in function display_status_2()
in utils/gssd/gss_util.c, so you could change its priority as well.

I haven't tried this, but have you tried setting "verbosity" to "-1"?
That should result in no messages being logged.  That does mean *all*
messages would be silenced though.

K.C.