From: Steve Dickson <SteveD@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/1] statd: Decouple statd's state directory from the NFS state directory
Date: Tue, 20 Sep 2011 12:16:50 -0400 [thread overview]
Message-ID: <4E78BC72.40303@RedHat.com> (raw)
In-Reply-To: <20110920154011.GA6959@infradead.org>
On 09/20/2011 11:40 AM, Christoph Hellwig wrote:
> On Tue, Sep 20, 2011 at 11:03:40AM -0400, Steve Dickson wrote:
>> To allow greater flexibility to where statd's state is kept,
>> statd's state path can now be decoupled from the normal
>> NFS state directory.
>>
>> In configure.ac, the NSM_STATD_PATH definition will now define
>> the path to where the state information is kept. The default
>> value, /var/lib/nfs, can be redefined with the --with-statdpath
>> flag.
>
> What is thje rationale for this? And who would want to move it at
> compile time, not at run time?
It all has to do with statd not running as root...
During the rpm installation, a state directory is created and
the uid/gid are set to rpcuser id. When statd fires up, those
uid/gids are obtained and used to set the process's uid/gid so
the daemon does not run as root..
The default NFS state directory is /var/lib/nfs. Since other
processes, like mountd and exportfs, read and write to that,
we don't want to muck around with its ownership. So a statd
directory is created and the ownership of that directory
is mucked with.
steved.
next prev parent reply other threads:[~2011-09-20 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 15:03 [PATCH 1/1] statd: Decouple statd's state directory from the NFS state directory Steve Dickson
2011-09-20 15:40 ` Christoph Hellwig
2011-09-20 16:16 ` Steve Dickson [this message]
2011-09-20 16:19 ` Christoph Hellwig
2011-09-20 16:33 ` Chuck Lever
2011-09-20 15:43 ` Chuck Lever
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=4E78BC72.40303@RedHat.com \
--to=steved@redhat.com \
--cc=hch@infradead.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;
as well as URLs for NNTP newsgroup(s).