Received-SPF: pass (google.com: domain of linux-nfs+bounces-2697-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Precedence: bulk
MIME-Version: 1.0
References: <CAEdQ38GJgxponxNxkcv+t8mhwRPzOjan58MTBgOL8p9tY=rvTw@mail.gmail.com>
 <79c69668-4f8e-448e-9f50-6977cda662fc@redhat.com>
In-Reply-To: <79c69668-4f8e-448e-9f50-6977cda662fc@redhat.com>
From: Matt Turner <mattst88@gmail.com>
Date: Sat, 6 Apr 2024 18:26:10 -0400
Message-ID: <CAEdQ38FOP0_g0FK5DYz954OwfJjLUf2pjQL1CX=VNC60kd8HEw@mail.gmail.com>
Subject: Re: nfs-utils' .service files not usable with nfsv4-server.service
To: Steve Dickson <steved@redhat.com>
Cc: linux-nfs@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Apr 6, 2024 at 4:37=E2=80=AFPM Steve Dickson <steved@redhat.com> wr=
ote:
>
> Hello,
>
> On 4/5/24 10:29 AM, Matt Turner wrote:
> > Downstream bug: https://bugs.gentoo.org/928526
> >
> > In Gentoo we allow disabling NFSv3 support, which entails nothing more
> > than not installing `nfs-server.service`. This has uncovered an issue
> > that many .service files reference `nfs-server.service` explicitly,
> > making them unusable with `nfsv4-server.service`.
> Very interesting... not supporting v3... Just curious as to why?

I don't think there's a particularly compelling reason. I guess it
lets you avoid a dependency on rpcbind.

> >> server ~ # grep nfs-server.service $(qlist nfs-utils | grep service)
> >> /usr/lib/systemd/system/rpc-statd-notify.service:After=3Dnfs-server.se=
rvice
> >> /usr/lib/systemd/system/nfs-mountd.service:BindsTo=3Dnfs-server.servic=
e
> >> /usr/lib/systemd/system/rpc-svcgssd.service:PartOf=3Dnfs-server.servic=
e
> >> /usr/lib/systemd/system/fsidd.service:Before=3Dnfs-mountd.service nfs-=
server.service
> >> /usr/lib/systemd/system/fsidd.service:RequiredBy=3Dnfs-mountd.service =
nfs-server.service
> >> /usr/lib/systemd/system/nfs-idmapd.service:BindsTo=3Dnfs-server.servic=
e
> >
> > The only service file that depends on nfsv4-server is nfsv4-exportd:
> >
> >> server ~ # grep nfsv4-server.service $(qlist nfs-utils | grep service)
> >> /usr/lib/systemd/system/nfsv4-exportd.service:BindsTo=3Dnfsv4-server.s=
ervice
> >
> > How should `nfsv4-server.service` be used?
> The idea was to make nfs-utils have a smaller footprint for containers.
> No rpcbind, lockd, statd etc.. exportd is to replace mountd
> and only accept v4 mounts.

Seems like we would just need to modify the build system to not
install `nfs-server.service` and other NFSv3-only service files and
modify the remaining service files to reference nfsv4-server.service
instead?

> Unfortunately the idea of having a nfsv4 only server
> did not go over well with upstream.

Which upstream do you mean? nfs-utils, Linux kernel?

> But, I will be more than willing to work with you to make it work.

Thanks!