Description of problem: While mountd, statd and lockd can be tied to a predefined port, the same is not true of rpc.rquotad. This makes firewalling hard! Version-Release number of selected component (if applicable): nfs-utils-1.0.6-22 How reproducible: Always Steps to Reproduce: 1. "service nfs restart" a few times 2. watch your partmapper "rpcinfo -p" 3. try firewalling that, matey! :) Actual results: works, but can't firewall easily Expected results: "man rquotad" say it'll accept "-p port", so why not? Additional info: Trivial patch to /etc/init.d/nfs to follow..
Created attachment 100663 [details] trivial fix Maybe one could include the "-S" functionality of rquotad later, too!
The rpc.rquotad from quota-3.10 (latest in fc2) has a bug in it. The -p option uses the port without first converting it to network byte order (htons). Newer quota packages from upstream have fixed this bug. A workaround is to specify the port in big endian (e.g. "rpc.rquotad -p 39426" for port 666).
This bug is no longer blocked now that bug 131594 and bug 131862 are fixed.
OK, I guess we should evaluate the patch from comment #1 and merge it, if it's still nedede with quota-3.12...
I've confirmed the patch works "as is" with the quota-3.12-5 RPM from FC3 test 3.
Fixed in nfs-utils-1.0.6-38
An update never went out for FC2, which this was filed against, but FC3 shipped with 1.0.6-39, which is greater than the version mentioned in comment #6.