linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian De Wolf <bldewolf@csupomona.edu>
To: Bryan Schumaker <bjschuma@gmail.com>
Cc: Linux NFS list <linux-nfs@vger.kernel.org>
Subject: Re: NFS uses wrong domain in SETATTR
Date: Tue, 6 Aug 2013 19:53:27 -0700	[thread overview]
Message-ID: <20130806195327.71323541@csupomona.edu> (raw)
In-Reply-To: <52015795.9060003@gmail.com>

On Tue, 6 Aug 2013 13:07:49 -0700
Bryan Schumaker <bjschuma@gmail.com> wrote:

> Hi Brian,
> 
> I'm sorry it took so long to reply to you, but you haven't been
> forgotten!  I've set up kerberos using freeipa on my own test system
> but I haven't been able to reproduce the bug you're seeing.  I had it
> working by using my kerberos domain set in /etc/idmap.conf and I saw
> the new domain go over the wire when I changed it in idmap.conf.  Do
> I need to do anything more to mimic your setup?
> 

Thanks for responding!  It seems like DNS might be where the wrong
kerberos domain is coming from.  Is your test client in the same domain
as your kerberos realm?  My clients aren't, and the subdomain they're
in is what is sent in the NFS requests.

I was able to test this by preferring files for hosts in nsswitch.conf
and overriding the host's name in /etc/hosts.  Normally the host is
under unx.csupomona.edu.  Moving the host to csupomona.edu in hosts
(and rebooting) causes chgrp to start working.  When I revert the
nsswitch and hosts changes chgrp keeps working until another reboot.

I hope this helps you reproduce this issue.  Let me know if there is
any other information you need.

  reply	other threads:[~2013-08-07  2:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19  0:41 NFS uses wrong domain in SETATTR Brian De Wolf
2013-08-06 20:07 ` Bryan Schumaker
2013-08-07  2:53   ` Brian De Wolf [this message]
2013-08-15 17:25     ` Bryan Schumaker
2013-08-16  1:40       ` Brian De Wolf

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=20130806195327.71323541@csupomona.edu \
    --to=bldewolf@csupomona.edu \
    --cc=bjschuma@gmail.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;
as well as URLs for NNTP newsgroup(s).