From c87a579a23b27e65ae956bc42cf0a247f2ca0baf Mon Sep 17 00:00:00 2001 From: Stephen Gallagher Date: Wed, 4 Apr 2012 06:33:11 -0700 Subject: Clean up log messages about keytab_name There were many places where we were printing (null) to the logs because a NULL keytab name tells libkrb5 to use its configured default instead of a particular path. This patch should clean up all uses of this to print "default" in the logs. https://fedorahosted.org/sssd/ticket/1288 --- src/providers/krb5/krb5_child.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'src/providers/krb5/krb5_child.c') diff --git a/src/providers/krb5/krb5_child.c b/src/providers/krb5/krb5_child.c index 6aeb7623f..209643a09 100644 --- a/src/providers/krb5/krb5_child.c +++ b/src/providers/krb5/krb5_child.c @@ -1273,8 +1273,10 @@ static krb5_error_code check_fast_ccache(krb5_context ctx, const char *primary, kerr = krb5_kt_default(ctx, &keytab); } if (kerr) { - DEBUG(0, ("Failed to read keytab file [%s].\n", - keytab_name != NULL ? keytab_name : "(default)")); + DEBUG(SSSDBG_FATAL_FAILURE, + ("Failed to read keytab file [%s]: %s\n", + KEYTAB_CLEAN_NAME, + sss_krb5_get_error_message(ctx, kerr))); goto done; } -- cgit