From: "J. Bruce Fields" <bfields@fieldses.org>
To: steve <steve@steve-ss.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: LOOKUP Reply Error:NFS3ERR_NO_ENT
Date: Wed, 25 Apr 2012 18:22:31 -0400 [thread overview]
Message-ID: <20120425222231.GE3251@fieldses.org> (raw)
In-Reply-To: <4F986927.9020102@steve-ss.com>
On Wed, Apr 25, 2012 at 11:14:15PM +0200, steve wrote:
> Sorry:
> also just seen this:
>
> CREATE Reply Error:NFS3ERR_ACCES
What principal are you authenticated as?
--b.
next prev parent reply other threads:[~2012-04-25 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 21:14 LOOKUP Reply Error:NFS3ERR_NO_ENT steve
2012-04-25 22:22 ` J. Bruce Fields [this message]
2012-04-25 23:27 ` steve
-- strict thread matches above, loose matches on Subject: below --
2012-04-25 21:06 steve
2012-04-25 22:20 ` J. Bruce Fields
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=20120425222231.GE3251@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=steve@steve-ss.com \
/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