Red Hat Bugzilla – Bug 159729
Default /etc/nsswitch.conf should not mention nisplus
Last modified: 2008-10-01 16:40:51 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Red Hat/1.0.4-1.4.1 Firefox/1.0.4
Description of problem:
/etc/nsswitch.conf contains various comments mentioning nisplus; however, nisplus is not supported by Red Hat or the upstream glibc developers. I would like to suggest the default nsswitch.conf be updated with fully-supported examples in the comments.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. cat /etc/nsswitch.conf
Actual Results: # Legal entries are:
# nisplus or nis+ Use NIS+ (NIS version 3)
#passwd: db files nisplus nis
#shadow: db files nisplus nis
#group: db files nisplus nis
# Example - obey only what nisplus tells us...
#services: nisplus [NOTFOUND=return] files
#networks: nisplus [NOTFOUND=return] files
#protocols: nisplus [NOTFOUND=return] files
#rpc: nisplus [NOTFOUND=return] files
#ethers: nisplus [NOTFOUND=return] files
#netmasks: nisplus [NOTFOUND=return] files
Expected Results: nisplus should be removed or replaced with nis since it's supported by Red Hat.
I'm trying to make it clear for end users that nisplus is not supported. Having examples mentioning nisplus is confusing for end users.
I had a bug open like this for years, not sure what happened to it. nisplus
isn't supported, and having it listed *does* take some cycles in the ns resolve
It is slower, it doesn't work with what Red Hat ships, and it isn't supported
anyway.... why is it still mentioned there?
This is also a problem in RHEL3
RHEL4 U2 initial glibc testing RPMs that should address also this problem
uploaded to ftp://people.redhat.com/jakub/glibc/2.3.4-2.10/
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.