Bug 1418041
Summary: | Update nfs-utils to use latest upstream configuration style | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Scott Mayhew <smayhew> |
Component: | nfs-utils | Assignee: | Steve Dickson <steved> |
Status: | CLOSED ERRATA | QA Contact: | Yongcheng Yang <yoyang> |
Severity: | medium | Docs Contact: | Milan Navratil <mnavrati> |
Priority: | medium | ||
Version: | 7.3 | CC: | chunwang, eguan, jiyin, jruemker, mnavrati, smayhew, yoyang |
Target Milestone: | rc | Keywords: | FutureFeature, Reproducer |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | nfs-utils-1.3.0-0.37.el7 | Doc Type: | Release Note |
Doc Text: |
Setting *nfs-utils* configuration options has been centralized in `nfs.conf`
With this update, *nfs-utils* uses configuration centralized in the `nfs.conf` file, which is structured into stanzas for each *nfs-utils* program. Each *nfs-utils* program can read the configuration directly from the file, so you no longer need to use the "systemctl restart nfs-config.service" command, but restart only the specific program. For more information, see the `nfs.conf(5)` manual page.
For compatibility with earlier releases, the older `/etc/sysconfig/nfs` configuration method is still available. However, it is recommended to avoid specifying configuration settings in both the `/etc/sysconfig/nfs` and `/etc/nfs.conf` file.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 19:48:51 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1358333 |
Description
Scott Mayhew
2017-01-31 16:53:52 UTC
Just checked the "Backward compatibility", i.e., when both old and new configuration exist and are conflict, the settings of old way (/etc/sysconfig/nfs) will be applied. -------------------------------------------------- [root@ibm-x3550m3-06 ~]# rpm -q nfs-utils nfs-utils-1.3.0-0.48.el7.x86_64 [root@ibm-x3550m3-06 ~]# cat /etc/sysconfig/nfs RPCNFSDARGS="--port 23456" [root@ibm-x3550m3-06 ~]# cat /etc/nfs.conf [nfsd] port=34567 [root@ibm-x3550m3-06 ~]# systemctl restart nfs-config [root@ibm-x3550m3-06 ~]# systemctl restart nfs [root@ibm-x3550m3-06 ~]# rpcinfo -p | grep -w nfs 100003 3 tcp 23456 nfs 100003 4 tcp 23456 nfs 100003 3 udp 23456 nfs 100003 4 udp 23456 nfs [root@ibm-x3550m3-06 ~]# -------------------------------------------------- However, if we just call the program directly, as it never use the old way (/etc/sysconfig/nfs) to configure it, and program can use settings from /etc/nfs.conf directly, it turns out the new way (/etc/nfs.conf) will be applied. -------------------------------------------------- [root@ibm-x3550m3-06 ~]# systemctl stop nfs [root@ibm-x3550m3-06 ~]# rpc.nfsd [root@ibm-x3550m3-06 ~]# rpcinfo -p | grep -w nfs 100003 3 tcp 34567 nfs 100003 4 tcp 34567 nfs 100003 3 udp 34567 nfs 100003 4 udp 34567 nfs [root@ibm-x3550m3-06 ~]# rpc.nfsd 0 [root@ibm-x3550m3-06 ~]# -------------------------------------------------- IMO, it is expected since calling program directly will start it by default settings previously before this modification. However, seems we'd better to generate some document to explain it some more. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2233 |