From: Steve Dickson <SteveD@redhat.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [nfs-utils RPC-PATCH 0/4] Add options to nfsd etc to avoid needing to write to /proc
Date: Sat, 08 Mar 2014 11:56:23 -0500 [thread overview]
Message-ID: <531B4BB7.9010303@RedHat.com> (raw)
In-Reply-To: <20140220063616.6548.42556.stgit@notabene.brown>
On 02/20/2014 01:36 AM, Neil Brown wrote:
> There are a number of NFS-related setting that currently must be set
> by writing to various files under /proc.
> This is a bit clumsy, particularly for systemd unit files.
>
> So this series adds options to a number of commands where relevant.
>
> The first two (rdma, and nfsv4{grace,lease}time) I am quite comfortable with.
> The third (nlm grace time) I think is probably right but if someone can argue
> an alternate approach I'm unlikely to resist.
> The fourth is .... uhm. You better look yourself.
>
> Part of me thinks that nlm port numbers should be set in /etc/sysctl.conf (or sysctl.d)
> and /etc/modprobe.d should have something like
>
> install lockd sysctl -p /etc/sysctl.d/lockd
>
> but last time I tried that it broke "modprobe --show-depends".
> Also it is awkward to get setting from /etc/sysconfig/nfs into /etc/sysctl.d/lockd
>
> Thoughts?
I finally got the cycles to take a look at these... My apologies for
taking so long...
So I went ahead took a look... Clean them up a bit. There were a couple
typos and they did not apply cleanly to my tree... While I was
doing this I got this gnawing feeling that we probably should have
some type of global configuration file where all these command
line variables can be set.
It would have to be distro friendly meaning the same place in all
distros... Maybe something like /etc/nfsclient.conf patterned off
the /etc/nfsmount.conf config file??
So I'm thinking it does make sense to have a way to set
all these but I'm just not keen on how they are being set.
IDK... Maybe I'm over thinking it.. :-)
Finally, during my testing the only flags that seem to work
was the statd ones:
# rpc.nfsd --rdma 8
rpc.nfsd: Unable to request RDMA services: Protocol not supported
# rpc.nfsd --grace-time 66
rpc.nfsd: Unable to set /proc/fs/nfsd/nfsv4gracetime: Device or resource busy
# rpc.nfsd --lease-time 66
rpc.nfsd: Unable to set /proc/fs/nfsd/nfsv4leasetime: Device or resource busy
Is this expected?
steved.
>
> Thanks,
> NeilBrown
>
>
> ---
>
> Neil Brown (4):
> nfsd: add -r and --rdma options to request rdma service.
> nfsd: alloc nfsv4leasetime and nfsv4gracetime to be set.
> nfsd: set nlm grace time to make NFSv4 grace time
> statd: add options to set port number of lockd.
>
>
> utils/nfsd/nfsd.c | 52 +++++++++++++++++++++++++++++++++++++++----
> utils/nfsd/nfsd.man | 21 +++++++++++++++++
> utils/nfsd/nfssvc.c | 59 +++++++++++++++++++++++++++++++++++++++++++++++++
> utils/nfsd/nfssvc.h | 2 ++
> utils/statd/statd.c | 57 +++++++++++++++++++++++++++++++++++++++++++++--
> utils/statd/statd.man | 24 ++++++++++++++++++--
> 6 files changed, 204 insertions(+), 11 deletions(-)
>
next prev parent reply other threads:[~2014-03-08 16:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 6:36 [nfs-utils RPC-PATCH 0/4] Add options to nfsd etc to avoid needing to write to /proc Neil Brown
2014-02-20 6:36 ` [PATCH 1/4] nfsd: add -r and --rdma options to request rdma service Neil Brown
2014-03-08 15:20 ` Steve Dickson
2014-03-10 0:10 ` NeilBrown
2014-02-20 6:36 ` [PATCH 4/4] statd: add options to set port number of lockd Neil Brown
2014-02-20 6:36 ` [PATCH 3/4] nfsd: set nlm grace time to make NFSv4 grace time Neil Brown
2014-02-20 16:40 ` J. Bruce Fields
2014-02-20 6:36 ` [PATCH 2/4] nfsd: alloc nfsv4leasetime and nfsv4gracetime to be set Neil Brown
2014-02-20 13:11 ` [nfs-utils RPC-PATCH 0/4] Add options to nfsd etc to avoid needing to write to /proc Trond Myklebust
2014-02-20 14:32 ` Chuck Lever
2014-02-25 1:37 ` NeilBrown
2014-02-25 1:44 ` Trond Myklebust
2014-02-25 1:47 ` Trond Myklebust
2014-03-08 16:56 ` Steve Dickson [this message]
2014-03-10 0:47 ` NeilBrown
2014-03-10 16:58 ` Steve Dickson
2014-03-12 5:43 ` NeilBrown
2014-03-11 16:05 ` Steve Dickson
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=531B4BB7.9010303@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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).