From: Steve Dickson <SteveD@redhat.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] gssd: cut down log chatter in gssd_search_krb5_keytab
Date: Thu, 07 Nov 2013 11:47:55 -0500 [thread overview]
Message-ID: <527BC43B.5070405@RedHat.com> (raw)
In-Reply-To: <1383839253-8223-1-git-send-email-jlayton@redhat.com>
Hello,
My thoughts...
On 07/11/13 10:47, Jeff Layton wrote:
> Because the kernel now looks for krb5 creds by default when mounting, we
> need to always have clients run rpc.gssd to avoid the 15s hang on the
> first mount attempt.
>
> In situations however where people don't have krb5 set up, this leads to
> a lot of log spamming on mount attempts. Try to cut down on some of the
> log chatter by lowering the priority of the log messages in
> gssd_search_krb5_keytab().
>
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
> ---
> utils/gssd/krb5_util.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/utils/gssd/krb5_util.c b/utils/gssd/krb5_util.c
> index 697d1d2..2ca3adc 100644
> --- a/utils/gssd/krb5_util.c
> +++ b/utils/gssd/krb5_util.c
> @@ -711,13 +711,13 @@ gssd_search_krb5_keytab(krb5_context context, krb5_keytab kt,
> */
> if ((code = krb5_kt_get_name(context, kt, kt_name, BUFSIZ))) {
> k5err = gssd_k5_err_msg(context, code);
> - printerr(0, "ERROR: %s attempting to get keytab name\n", k5err);
> + printerr(1, "ERROR: %s attempting to get keytab name\n", k5err);
> retval = code;
> goto out;
> }
> if ((code = krb5_kt_start_seq_get(context, kt, &cursor))) {
> k5err = gssd_k5_err_msg(context, code);
> - printerr(0, "ERROR: %s while beginning keytab scan "
> + printerr(1, "ERROR: %s while beginning keytab scan "
> "for keytab '%s'\n", k5err, kt_name);
> retval = code;
> goto out;
I'm thinking these need to stay... I don't think is a good idea
to mask out messages describing failures...
> @@ -727,7 +727,7 @@ gssd_search_krb5_keytab(krb5_context context, krb5_keytab kt,
> if ((code = krb5_unparse_name(context, kte->principal,
> &pname))) {
> k5err = gssd_k5_err_msg(context, code);
> - printerr(0, "WARNING: Skipping keytab entry because "
> + printerr(1, "WARNING: Skipping keytab entry because "
> "we failed to unparse principal name: %s\n",
> k5err);
> k5_free_kt_entry(context, kte);
> @@ -768,7 +768,7 @@ gssd_search_krb5_keytab(krb5_context context, krb5_keytab kt,
>
> if ((code = krb5_kt_end_seq_get(context, kt, &cursor))) {
> k5err = gssd_k5_err_msg(context, code);
> - printerr(0, "WARNING: %s while ending keytab scan for "
> + printerr(1, "WARNING: %s while ending keytab scan for "
> "keytab '%s'\n", k5err, kt_name);
> }
I think warnings would be ok to mask out...
steved.
>
>
next prev parent reply other threads:[~2013-11-07 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 15:47 [PATCH] gssd: cut down log chatter in gssd_search_krb5_keytab Jeff Layton
2013-11-07 15:58 ` Christoph Hellwig
2013-11-07 16:09 ` Jeff Layton
2013-11-07 16:21 ` Christoph Hellwig
2013-11-07 16:33 ` Jeff Layton
2013-11-07 16:35 ` Christoph Hellwig
2013-11-07 16:36 ` Jeff Layton
2013-11-07 16:38 ` Christoph Hellwig
2013-11-07 16:47 ` Steve Dickson [this message]
2013-11-07 16:56 ` Jeff Layton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=527BC43B.5070405@RedHat.com \
--to=steved@redhat.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox