Skip to contentSkip to conversation

nsswitch.conf.5: Current glibc reloads this configuration file

PATCH Superseded Florian Weimer 2 participants 3 messages Nov 4, 2022 Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 nsswitch.conf.5: Current glibc reloads this configuration file

The implementation happened across multiple glibc commits, but the work was completed for glibc 2.33.

---
 man5/nsswitch.conf.5 | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)
man5/nsswitch.conf.5 +7 -5
index 098585cf1..7049455ad 100644
@@ -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.
 .PP
 Traditionally, there was only a single source for service information,
 often in the form of a single configuration

base-commit: b106cd5bf43fe806100bb5266b78f92bac90b6e0

#1 lore raw

Hi Florian!

Quoted 4 lines · Florian Weimer

The implementation happened across multiple glibc commits, but the work was completed for glibc 2.33.

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

Quoted 15 lines
---
  man5/nsswitch.conf.5 | 12 +++++++-----
  1 file changed, 7 insertions(+), 5 deletions(-)
man5/nsswitch.conf.5 +0 -2
index 098585cf1..7049455ad 100644
@@ -402,11 +402,13 @@ for respective databases:
  .PD
  .RE
  .SH NOTES
-Within each process that uses
-.BR nsswitch.conf ,

man5/nsswitch.conf.5 for respective databases: · line 411

Quoted 10 lines
man5/nsswitch.conf.5 +7 -3
-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.

Quoted 6 lines
man5/nsswitch.conf.5 +0 -0
  .PP
  Traditionally, there was only a single source for service information,
  often in the form of a single configuration

base-commit: b106cd5bf43fe806100bb5266b78f92bac90b6e0

Signature · 1 line
<http://www.alejandro-colomar.es/>
#2 lore raw

* Alejandro Colomar:

Quoted 7 lines

Hi Florian!

Quoted 3 lines · Florian Weimer

The implementation happened across multiple glibc commits, but the work was completed for glibc 2.33.

Quoted 5 lines

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).

I'll try to remember that.

Quoted 5 lines

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?

It's in glibc 2.36. I don't have a manual page yet.

Thanks,
Florian