Description of problem: Change the value of LOCKDARG in /etc/sysconfig/nfs and then restart nfs-config.service. It seems that the arguments setting of LOCKDARG doesn't take effect. Even rebooting the machine cannot change the lockd setting neither. Maybe during the booting it has load it by a default setting. The lockd is a kernel module, we can only change it by unload and reload the lockd module. But how can we define the arguments? So is LOCKDARG in /etc/sysconfig/nfs useless, or the method to load it is with some problem? Seems the following code of /usr/lib/systemd/scripts/nfs-utils_env.sh seems never works: [root@hp-dl380pg8-01 ~]# cat /usr/lib/systemd/scripts/nfs-utils_env.sh ... [ -n "$LOCKDARG" ] && /sbin/modprobe lockd $LOCKDARG if [ -n "$LOCKD_TCPPORT" -o -n "$LOCKD_UDPPORT" ]; then [ -z "$LOCKDARG" ] && /sbin/modprobe lockd $LOCKDARG <snip> fi ...
nfs-utils-2.1.1-4.rc2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-bca43e3f7e
nfs-utils-2.1.1-4.rc2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-218c78b2e7
nfs-utils-2.1.1-4.rc2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
nfs-utils-2.1.1-4.rc2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.