From: Steve Dickson <steved@redhat.com>
To: Antonio Alvarez Feijoo <antonio.feijoo@suse.com>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/2] systemd: Allow nfs-idmapd.service to be started without the server
Date: Thu, 5 Jun 2025 06:53:10 -0400 [thread overview]
Message-ID: <495a075b-22ef-446d-97e5-e0f92ae19049@redhat.com> (raw)
In-Reply-To: <39e5050139e77397037f67705cf9d97fbe6a1520.1747753109.git.antonio.feijoo@suse.com>
On 5/22/25 2:59 AM, Antonio Alvarez Feijoo wrote:
> rpc.idmapd may be needed in the client if nfs4_disable_idmapping is
> set to 0. By replacing BindsTo= with PartOf=, nfs-idmapd.service can
> be started independently, and also affected if nfs-server.service is
> started or stopped.
>
> Signed-off-by: Antonio Alvarez Feijoo <antonio.feijoo@suse.com>
Committed... (tag: nfs-utils-2-8-4-rc2)
steved.
> ---
> systemd/nfs-idmapd.service | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/systemd/nfs-idmapd.service b/systemd/nfs-idmapd.service
> index d820f10c..3afdcea0 100644
> --- a/systemd/nfs-idmapd.service
> +++ b/systemd/nfs-idmapd.service
> @@ -6,7 +6,7 @@ Requires=rpc_pipefs.target
> After=rpc_pipefs.target local-fs.target network-online.target
> Wants=network-online.target
>
> -BindsTo=nfs-server.service
> +PartOf=nfs-server.service
>
> [Service]
> Type=forking
next prev parent reply other threads:[~2025-06-05 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 6:59 [PATCH 0/2] systemd: Handle nfsroot Antonio Alvarez Feijoo
2025-05-22 6:59 ` [PATCH 1/2] systemd: Allow nfs-idmapd.service to be started without the server Antonio Alvarez Feijoo
2025-06-05 10:53 ` Steve Dickson [this message]
2025-05-22 6:59 ` [PATCH 2/2] systemd: Add a generator to mount /sysroot via NFSv4 in the initrd Antonio Alvarez Feijoo
2025-06-05 10:53 ` 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=495a075b-22ef-446d-97e5-e0f92ae19049@redhat.com \
--to=steved@redhat.com \
--cc=antonio.feijoo@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox