public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Mention sudoers in nsswitch.conf(5)
Date: Thu, 6 Apr 2017 15:10:12 +0200	[thread overview]
Message-ID: <885caec0-dded-e22f-8b55-08f2868ad059@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 150 bytes --]

It turns out that sudo drops things into nsswitch.conf, too.  It has 
been suggested that we should mention this in the manual page.

Thanks,
Florian

[-- Attachment #2: sudoers.patch --]
[-- Type: text/x-patch, Size: 893 bytes --]

diff --git a/man5/nsswitch.conf.5 b/man5/nsswitch.conf.5
index 1e0ec3c..7a5b744 100644
--- a/man5/nsswitch.conf.5
+++ b/man5/nsswitch.conf.5
@@ -28,7 +28,7 @@ nsswitch.conf \- Name Service Switch configuration file
 .SH DESCRIPTION
 The Name Service Switch (NSS) configuration file,
 .IR /etc/nsswitch.conf ,
-is used by the GNU C Library to determine
+is used by the GNU C Library and certain other applications to determine
 the sources from which to obtain name-service information in
 a range of categories,
 and in what order.
@@ -102,6 +102,14 @@ Shadow user passwords, used by
 .BR getspnam (3)
 and related functions.
 .LP
+The GNU C Library ignores databases with unknown names.  Some
+applications use this to implement special handling for their own
+databases.  For example,
+.BR sudo (8)
+consults the
+.B sudoers
+database.
+.LP
 Here is an example
 .I /etc/nsswitch.conf
 file:

             reply	other threads:[~2017-04-06 13:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 13:10 Florian Weimer [this message]
     [not found] ` <885caec0-dded-e22f-8b55-08f2868ad059-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-04-10 11:35   ` Mention sudoers in nsswitch.conf(5) 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=885caec0-dded-e22f-8b55-08f2868ad059@redhat.com \
    --to=fweimer-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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