From: Steve Dickson <steved@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: [RFC PATCH 0/1] Enable config.d directory to be processed.
Date: Thu, 29 Oct 2020 17:04:00 -0400 [thread overview]
Message-ID: <20201029210401.446244-1-steved@redhat.com> (raw)
The following patch looks for config.d directories
and configuration file in those directories will
be loaded.
For example if /etc/nfs.conf.d or /etc/nfsmount.conf.d
exists and there are config files in those directories
will be loaded, but not the actual /etc/nfs.conf or
the /etc/nfsmount.conf files will not be.
I do have a couple questions/concerns
1) Is calling conf_load_file() more than once
kosher... It appears variable will just be
over written. That does appear to happen
with my testing.
2) If conf.d file(s) do exist, should the give
flat conf file also be loaded. At this point if
the conf.d file(s) do exist, then the given
flat config file is not loaded.
3) How to document this new feature.
Steve Dickson (1):
conffile: process config.d directory config files.
support/nfs/conffile.c | 78 +++++++++++++++++++++++++++++++++++++++++-
1 file changed, 77 insertions(+), 1 deletion(-)
--
2.26.2
next reply other threads:[~2020-10-29 21:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 21:04 Steve Dickson [this message]
2020-10-29 21:04 ` [PATCH 1/1] conffile: process config.d directory config files Steve Dickson
2020-11-02 13:03 ` [RFC PATCH 0/1] Enable config.d directory to be processed Alice Mitchell
2020-11-02 13:24 ` Steve Dickson
2020-11-02 14:23 ` Steve Dickson
2020-11-02 15:05 ` Alice Mitchell
2020-11-02 15:16 ` Chuck Lever
2020-11-02 16:37 ` Steve Dickson
2020-11-02 16:42 ` Steve Dickson
2020-11-02 15:57 ` Alice Mitchell
2020-11-02 19:42 ` Steve Dickson
2020-11-02 22:01 ` McIntyre, Vincent (CASS, Marsfield)
2020-11-03 10:14 ` Alice Mitchell
2020-11-03 17:16 ` Steve Dickson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201029210401.446244-1-steved@redhat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox