public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] nsswitch.conf.5: Current glibc reloads this configuration file
Date: Fri, 4 Nov 2022 17:58:01 +0100	[thread overview]
Message-ID: <787f1231-3370-dd8f-3353-e95ea293bbff@gmail.com> (raw)
In-Reply-To: <87mt96zmxs.fsf@oldenburg.str.redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 2422 bytes --]

Hi Florian!

On 11/4/22 17:47, Florian Weimer wrote:
> The implementation happened across multiple glibc commits, but the work
> was completed for glibc 2.33.
> 
> Signed-off-by: Florian Weimer <fweimer@redhat.com>

Thanks for the patch!

May I ask that you CC me in patches?  I sometimes miss patches sent only to the 
list.  (If there are any other patches from you that I ignored, please ping).

See a minor formatting comment below.

BTW, I remember some month ago having followed the discussion about adding 
arc4random(3).  Did you finally add it?  If so, would any of you (glibc 
programmers) mind sending a manual page?

Thanks a lot!

Cheers,

Alex

> 
> ---
>   man5/nsswitch.conf.5 | 12 +++++++-----
>   1 file changed, 7 insertions(+), 5 deletions(-)
> 
> diff --git a/man5/nsswitch.conf.5 b/man5/nsswitch.conf.5
> index 098585cf1..7049455ad 100644
> --- a/man5/nsswitch.conf.5
> +++ b/man5/nsswitch.conf.5
> @@ -402,11 +402,13 @@ for respective databases:
>   .PD
>   .RE
>   .SH NOTES
> -Within each process that uses
> -.BR nsswitch.conf ,
> -the entire file is read only once.
> -If the file is later changed, the
> -process will continue using the old configuration.
> +Starting with glibc 2.33,
> +.\" https://sourceware.org/bugzilla/show_bug.cgi?id=12459
> +.B nsswitch.conf
> +is automatically reloaded if the file is changed.  In earlier
> +versions, the entire file was read only once within each process, and
> +if the file was later changed, the process would continue using the
> +old configuration.

Would you please reformat to use semantic line breaks?

man-pages(7):
    Use semantic newlines
        In  the  source of a manual page, new sentences should be
        started on new lines, long sentences should be split into
        lines at clause breaks (commas, semicolons,  colons,  and
        so on), and long clauses should be split at phrase bound‐
        aries.   This  convention,  sometimes  known as "semantic
        newlines", makes it easier to see the effect of  patches,
        which often operate at the level of individual sentences,
        clauses, or phrases.

>   .PP
>   Traditionally, there was only a single source for service information,
>   often in the form of a single configuration
> 
> base-commit: b106cd5bf43fe806100bb5266b78f92bac90b6e0
> 

-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-11-04 16:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 16:47 [PATCH] nsswitch.conf.5: Current glibc reloads this configuration file Florian Weimer
2022-11-04 16:58 ` Alejandro Colomar [this message]
2022-11-04 17:50   ` Florian Weimer

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=787f1231-3370-dd8f-3353-e95ea293bbff@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=linux-man@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