From: James Bardin <jbardin@bu.edu>
To: nfs@lists.sourceforge.net
Subject: Re: nfs sec=krb5 on RHEL and CentOS
Date: Thu, 25 Jan 2007 14:43:11 -0500 [thread overview]
Message-ID: <45B9084F.7090307@bu.edu> (raw)
In-Reply-To: <a3b675320701241614p360a596fjb92723eb5ce6dfd9@mail.gmail.com>
I'm almost there!
Between the nfs-utils patch, and the noacl option, I have my 32bit
systems working. (thanks Steve)
On x86_64, I'm having kerberos problems (exact same config):
rpc.gssd[4871]: handling krb5 upcall
rpc.gssd[4871]: getting credentials for client with uid xxxx for server
yyyy.bu.edu
rpc.gssd[4871]: CC file 'krb5cc_xxxx_bSULEy' being considered
rpc.gssd[4871]: CC file 'krb5cc_xxxx_bSULEy' matches name check and has
mtime of 1169750861
rpc.gssd[4871]: using FILE:/tmp/krb5cc_xxxx_bSULEy as credentials cache
for client with uid xxxx for server yyyy.bu.edu
rpc.gssd[4871]: creating context using euid xxxx (save_uid 0)
rpc.gssd[4871]: creating tcp client for server yyyy.bu.edu
rpc.gssd[4871]: WARNING: can't create rpc_clnt for server engna1.bu.edu
for user with uid xxxx: RPC: Success
rpc.gssd[4871]: WARNING: Failed to create krb5 context for user with uid
xxxx for server yyyy.bu.edu
rpc.gssd[4871]: doing error downcall
-jim
>> Try using the -o noacl mount option...
>>
>> steved.
>>
>
> Steved,
> Ok, this seems to be it. ( I'll try out some other configuration/64bit
> tomorrow)
> Could you give me a brief summary on why this is happening, and only
> on this kernel? Mostly, should I always be using noacl when the netapp
> is handling file access?
>
> thanks
> -jim
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-01-25 19:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 22:11 nfs sec=krb5 on RHEL and CentOS james bardin
2007-01-24 11:05 ` Steve Dickson
2007-01-24 15:03 ` James Bardin
2007-01-24 20:58 ` James Bardin
2007-01-24 23:39 ` J. Bruce Fields
2007-01-25 0:14 ` james bardin
2007-01-25 19:43 ` James Bardin [this message]
2007-01-25 21:56 ` James Bardin
2007-01-25 23:14 ` Kevin Coffman
2007-01-25 23:40 ` James Bardin
2007-01-26 17:07 ` James Bardin
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=45B9084F.7090307@bu.edu \
--to=jbardin@bu.edu \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.