Bug 153974

Summary: Changes in NIS database are only visible for getent/NSS after ypserv restart
Product: Red Hat Enterprise Linux 3 Reporter: Florian Brand <florian.brand>
Component: ypservAssignee: Steve Dickson <steved>
Status: CLOSED WONTFIX QA Contact: Jay Turner <jturner>
Severity: low Docs Contact:
Priority: medium    
Version: 3.0CC: srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-19 19:05:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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):
ypserv-2.8-11

How reproducible:
Always

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:

Workaround:
service ypserv restart

Comment 1 RHEL 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:
http://www.redhat.com/security/updates/errata/
 
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.