public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Anthony Rossomano <trossoma2@gmail.com>, linux-nfs@vger.kernel.org
Subject: Re: Path for rpc_pipefs
Date: Wed, 04 Jun 2025 10:13:41 -0400	[thread overview]
Message-ID: <5e3f1c5595e266bcb91e0e6db0b308feae6497fc.camel@kernel.org> (raw)
In-Reply-To: <B7AF8E7A-65BC-4DF5-A590-00E4B2F0B5D5@gmail.com>

On Tue, 2025-06-03 at 15:38 -0700, Anthony Rossomano wrote:
> I wanted to get some input about changing the path to rpc_pipefs mount point. Can this be done and how to do it. The mount unit provided by nfs-utils pkg is cfg’d with path to /var/lib/nfs/rpc_pipefs but you can change the path for dependent services in /etc/nfs.conf. Can a new mount unit be created to change the mount path? Env is Alma 8. Having trouble because mount point is created early and need to remount /var elsewhere later, and need to deal with the rpc_pipefs mount point. Changes to systemd dependencies are not panning out. Thanks in advance for any input

Most of the daemons that work with rpc_pipefs take a command-line
parameter to change where the rpc_pipefs mountpoint is. Adding matching
config options to nfs.conf would probably not be too difficult.

I suggest pulling down the nfs-utils tree [1], and look at how the
nfs.conf handling is done. Find the places where the rpc_pipefs
directory path is set and have them check the config file for the
default and fall back to the compile-time default if it's not set.

FWIW, it looks like blkmapd already has a config file parameter for
this, so mirroring that for the other daemons is probably what you want
to aim for.

[1]: git://git.linux-nfs.org/projects/steved/nfs-utils.git
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2025-06-04 14:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03 22:38 Path for rpc_pipefs Anthony Rossomano
2025-06-04 14:13 ` Jeff Layton [this message]
2025-06-04 22:43   ` Scott Mayhew

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=5e3f1c5595e266bcb91e0e6db0b308feae6497fc.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trossoma2@gmail.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