From: "Brian J. Murrell" <brian-SquOHqY54CVWr29BmMi2cA@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: NFSv4 and EPERM for all but one user
Date: Sat, 28 Nov 2009 16:46:45 -0500 [thread overview]
Message-ID: <1259444804.13762.29.camel@pc.interlinx.bc.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]
I have an NFSv4 export configured on a server with kernel
2.6.24-24-generic:
/usr/local pc(sec=krb5,rw,no_root_squash,sync,subtree_check) \
pvr(sync,subtree_check)
On the machine "pc" one user (me) is able to read it:
$ sudo su - brian -c "ls -l /usr/local"
total 36
drwxr-xr-x 2 root root 4096 2009-06-19 10:05 bin
drwxr-xr-x 4 root root 4096 2009-01-01 09:56 Brother
drwxr-xr-x 2 root root 4096 2008-11-29 10:49 etc
drwxr-xr-x 2 root root 4096 2007-03-24 21:01 games
drwxr-xr-x 2 root root 4096 2007-03-24 21:01 include
drwxr-xr-x 7 root root 4096 2009-08-02 11:54 lib
lrwxrwxrwx 1 root root 9 2007-03-24 21:01 man -> share/man
drwxr-xr-x 2 root root 4096 2007-03-24 21:01 sbin
drwxr-xr-x 12 root root 4096 2009-07-07 08:40 share
drwxr-xr-x 2 root root 4096 2007-03-24 21:01 src
But any other user is not:
$ sudo su - brianm -c "ls -l /usr/local"
No directory, logging in with HOME=/
bind: Address already in use
ls: cannot open directory /usr/local: Permission denied
$ sudo su - nobody -c "ls -l /usr/local"
No directory, logging in with HOME=/
bind: Address already in use
ls: cannot open directory /usr/local: Permission denied
This filesystem is mounted with autofs on "pc" which is running
2.6.30-10-generic:
/usr/local -fstype=nfs4,sec=krb5 linux:/usr/local
I'm positive this is PEBKAC but I'm not sure of what nature.
Any ideas?
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
reply other threads:[~2009-11-28 21:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1259444804.13762.29.camel@pc.interlinx.bc.ca \
--to=brian-squohqy54cvwr29bmmi2ca@public.gmane.org \
--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