I don't need rpcbind, as I only use NFSv4. Is there any way to set up or configure the NFS server-related units (nfs-server.service, etc.) to not start rpcbind?
Once upon a time, Ian Pilcher arequipeno@gmail.com said:
I don't need rpcbind, as I only use NFSv4. Is there any way to set up or configure the NFS server-related units (nfs-server.service, etc.) to not start rpcbind?
This is from Red Hat's RHEL 8 docs, but works the same on Fedora (at least version 35). Set 'vers3=n' in the '[nfsd]' section of /etc/nfs.conf, mask the RPC services, and restart NFS:
systemctl mask --now rpc-statd.service rpcbind.service rpcbind.socket systemctl restart nfs-server
https://access.redhat.com/documentation/zh-cn/red_hat_enterprise_linux/8/htm...
On 5/28/22 10:18, Chris Adams wrote:
This is from Red Hat's RHEL 8 docs, but works the same on Fedora (at least version 35). Set 'vers3=n' in the '[nfsd]' section of /etc/nfs.conf, mask the RPC services, and restart NFS:
systemctl mask --now rpc-statd.service rpcbind.service rpcbind.socket systemctl restart nfs-server
Thanks!
The /etc/nfs.conf change was the key, as it allows the server to start with the various rpc* units masked.
I actually ended up masking even more RPC-related units. No apparent ill effects thus far.
lrwxrwxrwx. 1 root root 9 May 29 10:39 rpcbind.service -> /dev/null lrwxrwxrwx. 1 root root 9 May 29 10:39 rpcbind.socket -> /dev/null lrwxrwxrwx. 1 root root 9 May 29 10:40 rpcbind.target -> /dev/null lrwxrwxrwx. 1 root root 9 May 29 10:41 rpc_pipefs.target -> /dev/null lrwxrwxrwx. 1 root root 9 May 29 10:46 rpc-statd-notify.service -> /dev/null lrwxrwxrwx. 1 root root 9 May 29 10:39 rpc-statd.service -> /dev/null