Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/2] nfs-utils: systemd units bug fixes and comments.
Date: Tue, 18 Feb 2014 16:14:45 -0500	[thread overview]
Message-ID: <5303CD45.1010208@RedHat.com> (raw)
In-Reply-To: <C4E26F58-0097-4200-9860-8F8B8172B627@oracle.com>



On 02/18/2014 02:36 PM, Chuck Lever wrote:
>> At this point its a pipe dream for rpc.gssd to run with no keytab.
> This is not a pipe dream. 
I meant its a pipe dream in the current state due to, your nicely 
termed, "gssd log diarrhea" ;-) 

steved.
 
> I’m talking about the common use case where a user kinit’s as root then uses the “-n” option on gssd so that root’s credential is used as the client’s machine credential, instead of using the keytab to establish a GSS context.
> 
> With the exception of kernels 3.9 - 3.12, this has always worked, does require gssd to be running, and does not need to have a keytab on the client to operate correctly.  When 3.9 broke this feature, people (including NeilB!) complained loudly.
> 
>> > It logs a ton of errors messages on every upcall which means 
>> > on every mount these days.
>> > We either have to tone down the error messages or check for the 
>> > existence of the keytab before processing the upcall.
>> > I think the latter would better… 
> gssd default verbosity is a legacy of the days when Kerberized NFS was new and we wanted verbose logging to monitor gssd activity.  It seems like a harmless step forward to eliminate them or hide some or all of them behind a gssd command line option.
> 
> The bug here is gssd log diarrhea.

  reply	other threads:[~2014-02-18 21:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18  8:48 [PATCH 0/2] nfs-utils: systemd units bug fixes and comments Steve Dickson
2014-02-18  8:48 ` [PATCH 1/2] rpc-svcgssd.service: removed a the start up triggers Steve Dickson
2014-02-19  3:17   ` NeilBrown
2014-02-19 16:03     ` Simo Sorce
2014-02-19 22:19       ` NeilBrown
2014-02-18  8:48 ` [PATCH 2/2] systemd: Removed the "ordering cycle" from nfs-server.service Steve Dickson
2014-02-19  3:21   ` NeilBrown
2014-02-18 14:29 ` [PATCH 0/2] nfs-utils: systemd units bug fixes and comments Chuck Lever
2014-02-18 18:44   ` Steve Dickson
2014-02-18 19:36     ` Chuck Lever
2014-02-18 21:14       ` Steve Dickson [this message]
2014-02-19  6:57 ` NeilBrown

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=5303CD45.1010208@RedHat.com \
    --to=steved@redhat.com \
    --cc=chuck.lever@oracle.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