From: Matthew Ward <matthew.ward@fubra.com>
To: linux-nfs@vger.kernel.org
Subject: Re: Issue with NFS and LDAP, attribute caching with "Permission denied"
Date: Thu, 07 Jul 2011 16:10:21 +0100 [thread overview]
Message-ID: <4E15CC5D.6070108@fubra.com> (raw)
In-Reply-To: <4E15C555.9030002@fubra.com>
Using exportfs -rf seems to solve the issue, and I'm happy that it's not
going to happen often enough and not cause too much of a performance hit
to be happily run every time we add a random user and group to the
server. If anyone has any further insight, I'd be happy to discuss.
============
Matthew Ward
Web and Mobile Application Developer
Fubra Limited
w: www.fubra.com
e: matthew.ward@fubra.com
------------------------------
Fubra is a company limited by shares and registered in England and
Wales with number 3967214 at Anstey Park House, Anstey Road,
Alton, Hampshire, GU34 2RL. We are registered for VAT with number
GB733667024, and as a data controller with number Z5193400.
We are members of RIPE, Nominet, The Italian RA and registered
with OfCom as a provider of electronic communications services.
prev parent reply other threads:[~2011-07-07 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 14:40 Issue with NFS and LDAP, attribute caching with "Permission denied" Matthew Ward
2011-07-07 15:10 ` Matthew Ward [this message]
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=4E15CC5D.6070108@fubra.com \
--to=matthew.ward@fubra.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 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.