Nfs.conf

🔗 Change Proposal Name

• Deprecating /etc/sysconfig/nfs

🔗 Summary

• Deprecate /etc/sysconfig/nfs and only use /etc/nfs.conf to configure NFS daemons.

🔗 Owner

• Name: Steve Dickson
• Email: steved@redhat.com
• Release notes owner:

🔗 Current status

• Targeted release: Fedora 30
• Last updated: 2018-10-13
• Tracker bug: <will be assigned by the Wrangler>

🔗 Detailed Description

Since the beginning /etc/sysconfig/nfs has been used to configure the NFS server daemons by supply command line arguments to the daemons or commands via SysVinit scripts.

Then systemd(1) came along and the idea of daemons self-configuration was started. Meaning daemons and commands would get their configurations from a file, not the command line like with SysVinit scripts.

Back in late 2016, Neil Brown from SuSe, implemented this changed. He built into each daemon the ability to read from one central file, /etc/nfs.conf. See nfs.conf(5) for details.

After this work made it upstream, I a wrote patch that added back the ability to use /etc/sysconfig/nfs to maintain backwards compatibility which has lasted for the last few Fedora releases.

I think at this point, the timing is right to introduce this single file configuration to Fedora 30.

🔗 Benefit to Fedora

• Having a single file configuration will help IT automation systems like Ansible configure NFS servers.
• This change also simplifies the systemd scrips.
• Having two ways of configuring NFS is not desirable. The only reason there has been no problems is because nobody know about /etc/nfs.conf
• There is a new command, nfsconf(8), that checks the correctness of /etc/nfs.conf

🔗 Scope

• Proposal owners: Steve Dickson <steved@redhat.com>
• Other developers: Justin Mitchell <jumitche@redhat.com>
• Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
• List of deliverables: N/A (not a System Wide Change)
• Policies and guidelines: N/A (not a System Wide Change)
• Trademark approval: N/A (not needed for this Change)

🔗 Upgrade/compatibility impact

🔗 How To Test N/A (not a System Wide Change)

🔗 User Experience

🔗 Dependencies N/A (not a System Wide Change)

🔗 Contingency Plan

• Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
• Contingency deadline: N/A (not a System Wide Change)
• Blocks release? N/A (not a System Wide Change), Yes/No
• Blocks product? product

🔗 Documentation N/A (not a System Wide Change)

🔗 Release Notes