Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Steve Dickson <steved@redhat.com>
To:     Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/3 V2]  Enable config.d directory to be processed.
Date:   Thu,  5 Nov 2020 09:56:31 -0500
Message-Id: <20201105145634.98281-1-steved@redhat.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Here is the second attempt to use conf.d directories
to set configuration variables. 

When a conf.d directory exists and files with the
".conf" extension exist they will be used to set
configuration variables. 

Files not using that extension or files beginning 
with a "." (ex .nfs.conf) will be ignored. 

The conf.d files will take priority over the main 
config files. Meaning a variable set in both the
main config and the conf.d file, the conf.d file
will have priority over the variable in the main config.

The ordering of when the conf.d are processed
can be set by alphabetical naming convention.
Prefixing file name with a 001-nfs.conf, 
002-nfs.conf will control when the config is 
process. Note the last config file process
with have the highest priority.

Steve Dickson (3):
  conffile: process config.d directory config files.
  conffile: Only process files in the config.d dirs that end with ".conf"
  manpage: Update nfs.conf and nfsmount.conf manpages

 support/nfs/conffile.c        | 139 +++++++++++++++++++++++++++++++++-
 systemd/nfs.conf.man          |   8 ++
 utils/mount/nfsmount.conf.man |   7 ++
 3 files changed, 151 insertions(+), 3 deletions(-)

-- 
2.26.2