Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 153974 - Changes in NIS database are only visible for getent/NSS after ypserv restart
Summary: Changes in NIS database are only visible for getent/NSS after ypserv restart
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: ypserv
Version: 3.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Jay Turner
Depends On:
TreeView+ depends on / blocked
Reported: 2005-04-06 10:33 UTC by Florian Brand
Modified: 2015-01-08 00:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-10-19 19:05:24 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Florian Brand 2005-04-06 10:33:16 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Firefox/1.0.2 Fedora/1.0.2-1.3.1

Description of problem:
after adding a new user and recreating the NIS database ypcat shows the new user while getent passwd does not. After restarting ypserv getent works as expected 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. nisserver# useradd foo
2. nisserver# make -C /var/yp
3. nisclient# ypcat passed | grep foo
   foo:X:505: ...

Actual Results:  4. nisclient# getent passwd | grep foo
   [no response]

Expected Results:  4. nisclient# getent passwd | grep foo
   foo:X:505: ...

Additional info:

service ypserv restart

Comment 1 RHEL Product and Program Management 2007-10-19 19:05:24 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

Note You need to log in before you can comment on or make changes to this bug.