All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: linux-man@vger.kernel.org
Subject: [PATCH] nsswitch.conf.5: Current glibc reloads this configuration file
Date: Fri, 04 Nov 2022 17:47:27 +0100	[thread overview]
Message-ID: <87mt96zmxs.fsf@oldenburg.str.redhat.com> (raw)

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

Signed-off-by: Florian Weimer <fweimer@redhat.com>

---
 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.
 .PP
 Traditionally, there was only a single source for service information,
 often in the form of a single configuration

base-commit: b106cd5bf43fe806100bb5266b78f92bac90b6e0


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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 16:47 Florian Weimer [this message]
2022-11-04 16:58 ` [PATCH] nsswitch.conf.5: Current glibc reloads this configuration file Alejandro Colomar
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=87mt96zmxs.fsf@oldenburg.str.redhat.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.