Page 1 of 1
Here's rpcbind.sfs. Please add to the Fatdog repo
Posted: Tue Nov 16, 2021 7:03 pm
by chiron
Hi,
I've been toying around with NFS recently again, and tried to set up an NFS Server with Fatdog 8.11. Found out, rpcbind is missing. Sourced the correct version (corresponding to NFS-Utils and libtirpc) from LFS and compiled. Additionally, two scripts in init.d were needed, nfs-server and rpcbind, also sourced from LFS site ans slightly modified.
Put it together in an sfs and attached it. My skills in building packages are, lets say, limited.
Re: [Request] Please add rpcbind, at least in the repo
Posted: Tue Nov 16, 2021 9:37 pm
by step
Thank you, chiron. I just want to add that, If in addition to controlling the server's configuration you can also control the client's mounts, you should be able to mount the remote file system even without running rpcbind. The idea is to fix the service port number(s) on the server, and to specify these fixed port numbers in the mount command's mountport option on the clients. Of course, if the client is a zip-locked system where mount options can't be changed, this solution isn't feasible.
Re: [Request] Please add rpcbind, at least in the repo
Posted: Wed Nov 17, 2021 12:43 pm
by chiron
Ah, OK, so it should run without rpcbind on the servers end?
The nfs-server script in init.d would be enough, given that it specifies a port to listen?
Could actually be that way, since I copied the four files over in one go and then it worked.
So one could disable rpcbind and it would still work. Didn't find much documentation on that, everywhere it says that rpcbind is required.
Re: [Request] Please add rpcbind, at least in the repo
Posted: Thu Nov 18, 2021 8:30 pm
by step
chiron wrote: ↑Wed Nov 17, 2021 12:43 pm
Didn't find much documentation on that, everywhere it says that rpcbind is required.
The NFS mount command manual page https://www.mankier.com/5/nfs tells the different role rpcbind takes when mounting from NFS version 2/3 vs. NFS version 4. rpcbind is used when the proto and mountproto options don't say otherwise. This is so that a system administrator can set up NFS mounts through a firewall that blocks rpcbind's default port, in other words, without rpcbind. If proto/mountproto isn't specified then rpcbind is needed. To speed up your reading the linked manual page, you could search for all "rpcbind" matches at least through the section about firewalls. I found a short answer to the question "Is rcpbind required for an NFS client?" here tough it's good to scan the manual to get more perspective.