public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chris Hall <linux-nfs@gmch.uk>
Cc: linux-nfs@vger.kernel.org
Subject: Re: mount.nfs4 and logging
Date: Sat, 19 Sep 2020 12:40:20 -0400	[thread overview]
Message-ID: <20200919164020.GB15785@fieldses.org> (raw)
In-Reply-To: <20200919163353.GA15785@fieldses.org>

On Sat, Sep 19, 2020 at 12:33:53PM -0400, J. Bruce Fields wrote:
> For the server, you don't need rpcbind or rpc.statd for v4, but you do
> need rpc.idmapd, rpc.mountd and nfsdcld.
> 
> rpc.mountd is the only one of those three that needs to listen on a
> network port, but that's only in the NFSv2/v3 case.  I'm not sure if
> we're getting that right.

Looking at the code, it looks correct--I see mountd starting those
listeners only when v2 or v3 are configured.

The documentation could be better, though.

--b.

  reply	other threads:[~2020-09-19 16:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <S1725851AbgIKKt5/20200911104957Z+185@vger.kernel.org>
2020-09-11 11:45 ` mount.nfs4 and logging Chris Hall
2020-09-14 18:30   ` Steve Dickson
2020-09-15 13:06     ` Chris Hall
2020-09-16 12:52       ` Kenneth Dsouza
2020-09-16 14:31       ` Kenneth Dsouza
2020-09-16 17:31       ` Kenneth Dsouza
2020-09-19 16:33       ` J. Bruce Fields
2020-09-19 16:40         ` J. Bruce Fields [this message]
     [not found]           ` <12298172-f830-4f22-8612-dfbbc74b8a40@gmch.uk>
2020-09-20 19:32             ` J. Bruce Fields
2020-09-21 14:40               ` Chris Hall
2020-09-23 14:40                 ` 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=20200919164020.GB15785@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@gmch.uk \
    --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