From: NeilBrown <neil@brown.name>
To: Steve Dickson <SteveD@RedHat.com>,
Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 2/2] mountd: Add debug processing from nfs.conf
Date: Tue, 09 Feb 2021 09:27:29 +1100 [thread overview]
Message-ID: <87sg66ci0e.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <66fbe743-aa9d-ca60-8955-c2859d9ab9df@RedHat.com>
[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]
On Mon, Feb 08 2021, Steve Dickson wrote:
> On 2/7/21 7:30 PM, NeilBrown wrote:
>> On Mon, Feb 01 2021, Steve Dickson wrote:
>>
>>> Signed-off-by: Steve Dickson <steved@redhat.com>
>>> ---
>>> nfs.conf | 2 +-
>>> utils/mountd/mountd.c | 3 +++
>>> 2 files changed, 4 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/nfs.conf b/nfs.conf
>>> index 186a5b19..9fcf1bf0 100644
>>> --- a/nfs.conf
>>> +++ b/nfs.conf
>>> @@ -30,7 +30,7 @@
>>> # udp-port=0
>>> #
>>> [mountd]
>>> -# debug=0
>>> +# debug="all|auth|call|general|parse"
>>> # manage-gids=n
>>> # descriptors=0
>>> # port=0
>>> diff --git a/utils/mountd/mountd.c b/utils/mountd/mountd.c
>>> index 988e51c5..a480265a 100644
>>> --- a/utils/mountd/mountd.c
>>> +++ b/utils/mountd/mountd.c
>>> @@ -684,6 +684,9 @@ read_mount_conf(char **argv)
>>> if (s && !state_setup_basedir(argv[0], s))
>>> exit(1);
>>>
>>> + if ((s = conf_get_str("mountd", "debug")) != NULL)
>>> + xlog_sconfig(s, 1);
>>> +
>>
>> Why is this needed?
>> A few lines higher up is
>> xlog_from_conffile("mountd");
>> which calls
>> kinds = conf_get_list(service, "debug");
>> and passes each word that it finds to xlog_sconfig()
>> ??
>>
>> I just tested setting "debug=all" in the mountd section of nfs.conf,
>> and it seems to work without this patch.
> No it is not... I didn't realize xlog_from_conffile() process
> the debug config variable... maybe we should change the name
> to something like xlog_debug_conffile()... something more
> descriptive as to what it does.
>
> I will clean it up... in a bit.
Thanks. I agree that including "debug" in that function name would
help. Maybe "conffile_set_debug()", or your suggestion.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]
next prev parent reply other threads:[~2021-02-08 22:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 23:01 [PATCH 1/2] mountd: Cleanup how config options are read in Steve Dickson
2021-02-01 23:01 ` [PATCH 2/2] mountd: Add debug processing from nfs.conf Steve Dickson
2021-02-02 17:03 ` Steve Dickson
2021-02-08 0:30 ` NeilBrown
2021-02-08 17:44 ` Steve Dickson
2021-02-08 22:27 ` NeilBrown [this message]
2021-02-02 17:02 ` [PATCH 1/2] mountd: Cleanup how config options are read in 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=87sg66ci0e.fsf@notabene.neil.brown.name \
--to=neil@brown.name \
--cc=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