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?
server ~ # grep nfs-server.service $(qlist nfs-utils | grep service)
/usr/lib/systemd/system/rpc-statd-notify.service:After=nfs-server.service
/usr/lib/systemd/system/nfs-mountd.service:BindsTo=nfs-server.service
/usr/lib/systemd/system/rpc-svcgssd.service:PartOf=nfs-server.service
/usr/lib/systemd/system/fsidd.service:Before=nfs-mountd.service nfs-server.service
/usr/lib/systemd/system/fsidd.service:RequiredBy=nfs-mountd.service nfs-server.service
/usr/lib/systemd/system/nfs-idmapd.service:BindsTo=nfs-server.service
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=nfsv4-server.service
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.
Unfortunately the idea of having a nfsv4 only server
did not go over well with upstream.
But, I will be more than willing to work with you to make it work.
steved.
Thanks,
Matt
