From: Peter Schiffer <pschiffe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: Mark R Bannister
<mark-/K+B3afwL8Jt0JrxVvvTASp2UmYkHbXO@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [patch] nsswitch.conf.5: clarify the "notfound" status
Date: Wed, 30 May 2012 11:22:42 +0200 [thread overview]
Message-ID: <4FC5E6E2.9070008@redhat.com> (raw)
In-Reply-To: <4F755DF2.3090906-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Hello,
I've updated the patch against the latest man-pages 3.41.
Also, I've added description of the initgroups database,
reformulated the note and moved it to the return action.
What do you think?
Thanks,
peter
--- nsswitch.conf.5.org 2012-05-10 22:13:23.000000000 +0200
+++ nsswitch.conf.5 2012-05-30 11:16:26.881542800 +0200
@@ -59,6 +59,11 @@
.BR gethostbyname (3)
and related functions.
.TP
+.B initgroups
+Supplementary group access list, used by
+.BR getgrouplist (3)
+function.
+.TP
.B netgroup
Network-wide list of hosts and users, used for access rules.
C libraries before glibc 2.1 supported netgroups only over NIS.
@@ -241,6 +246,10 @@
.B return
Return a result now.
Do not call any further lookup functions.
+However, for compatibility reasons, if this is the selected action
+for the `group' database and the `notfound' status,
+and the configuration file does not contain the `initgroups' line,
+the next lookup function is always called, without affecting the search
result.
.TP
.B continue
Call the next lookup function.
On 03/30/2012 09:17 AM, Peter Schiffer wrote:
> Hello guys,
>
> thanks for looking into this. I am adding some notes below:
>
> On 03/30/2012 01:27 AM, Michael Kerrisk (man-pages) wrote:
>> On Fri, Mar 30, 2012 at 10:31 AM, Mark R Bannister
>> <mark-/K+B3afwL8Jt0JrxVvvTASp2UmYkHbXO@public.gmane.org> wrote:
>>> On 29/03/2012 19:34, Michael Kerrisk (man-pages) wrote:
>>>> On Thu, Mar 29, 2012 at 9:09 AM, Mark R Bannister
>>>> <mark-/K+B3afwL8Jt0JrxVvvTASp2UmYkHbXO@public.gmane.org> wrote:
>>>>> On 28/03/2012 19:27, Peter Schiffer wrote:
>>>>>> Hello,
>>>>>>
>>>>>> I am suggesting the following update of the "notfound" status on
>>>>>> the
>>>>>> nsswitch.conf.5 man page. I am not 100% sure that this is the
>>>>>> correct
>>>>>> place
>>>>>> where this information on the man page should be placed. Any
>>>>>> comments
>>>>>> are
>>>>>> welcome.
>>>>>>
>>>>> Hi Peter,
>>>>>
>>>>> I did a rewrite of the nsswitch.conf man page in October last year:
>>>>>
>>>>> http://article.gmane.org/gmane.linux.man/2366/match=nsswitch+conf
>>>>>
>>>>> I'm still waiting for Michael to incorporate these changes. May I
>>>>> suggest
>>>>> you send in a patch that is applied against this? I would also
>>>>> suggest
>>>>> that
>>>>> if you're going to make reference to "initgroups" you'll need to
>>>>> add some
>>>>> further description somewhere that explains what this is and when you
>>>>> would
>>>>> use it.
>>>> Looking a little deeper at this, I'd like another set of eyes. Mark,
>>>> would you be able to review Peter's patch?
>>>>
>>>> Thanks,
>>>>
>>>> Michael
>>>>
>>> I can't find this comment in glibc myself, there's nothing to this
>>> effect in
>>> grp/initgroups.c ?
>> Follow Peter's URL.
>>
>>> I've tested on a build with glibc 2.5 - admittedly not the latest
>>> version
>>> but it does feature the initgroups functionality - and I am not
>>> witnessing
>>> this behaviour. My configuration file has no initgroups line, and this
>>> entry:
>>>
>>> group: db [NOTFOUND=return] files
>>>
>>> ...always returns as expected if my /var/db/group.db file does not
>>> contain
>>> the group entry that I am searching for.
>>>
>>> So I don't concur with the suggested change ...
> The result is always as expected, the added note should clarify how
> the search is done. Important example would be like this:
>
> group: files [!NOTFOUND=return] XXXXXX
>
> what means, according to the current text in the man page, that if the
> result from "files" is either SUCCESS, UNAVAIL or TRYAGAIN, then,
> it should be returned. Well, it is, but the XXXXXX is also _always_
> searched.
> Without the suggested note, it can be confusing while testing or
> setting up,
> also, if the XXXXXX is some remote service, this can create some hard
> to find
> delays.
>
> Thanks,
>
> peter
>> It looks like the change only arrived in glibc 2.14. Would you be able
>> to take a look there?
>>
>> Thanks,
>>
>> Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-05-30 9:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 18:27 [patch] nsswitch.conf.5: clarify the "notfound" status Peter Schiffer
[not found] ` <4F735800.6040807-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-03-28 20:09 ` Mark R Bannister
[not found] ` <4F737004.9060500-/K+B3afwL8Jt0JrxVvvTASp2UmYkHbXO@public.gmane.org>
2012-03-28 22:32 ` Michael Kerrisk (man-pages)
2012-03-29 18:34 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkispRXUer73r_HW2Oh+gjoHuj3e4t7dHFtSNDDorjBeHQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-29 21:31 ` Mark R Bannister
[not found] ` <4F74D4B6.7040701-/K+B3afwL8Jt0JrxVvvTASp2UmYkHbXO@public.gmane.org>
2012-03-29 23:27 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkjpoc53+hqghx3nOnKPxp+O=R7M4uwxtEXsH0cseLtvbA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-30 7:17 ` Peter Schiffer
[not found] ` <4F755DF2.3090906-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-05-30 9:22 ` Peter Schiffer [this message]
[not found] ` <4FC5E6E2.9070008-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-07-09 12:59 ` Peter Schiffer
[not found] ` <4FFAD5CE.5000903-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-08-13 8:47 ` Michael Kerrisk (man-pages)
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=4FC5E6E2.9070008@redhat.com \
--to=pschiffe-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark-/K+B3afwL8Jt0JrxVvvTASp2UmYkHbXO@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).