Bug 401171 - ypserv does not serve updated maps after make
Summary: ypserv does not serve updated maps after make
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: ypserv
Version: 4.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Karel Klíč
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-27 15:55 UTC by Gerben Roest
Modified: 2013-03-03 22:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-22 14:54:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gerben Roest 2007-11-27 15:55:45 UTC
Description of problem:

ypserv doesn't serve updated maps after make

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

ypserv-2.13-18

How reproducible:

always

Steps to Reproduce:

1. add user john
2. cd /var/yp;make
3. ypmatch john passwd
  
Actual results:

Can't match key john in map passwd.byname. Reason: No such key in map


Expected results:

john:$1$z3cbIx/7$tYUb3xbkaW8YD.NWyRRNu0:28890:28890::/home/john:/bin/bash

Additional info:

It only works after /etc/init.d/ypserv stop; /etc/init.d/ypserv start

Comment 1 Vitezslav Crhonek 2008-08-26 11:06:41 UTC
Sorry for late response, there was maintainer change.

You have probably something overlooked, because I'm not able to reproduce it. Do you have set right domainname on server, when updating maps? (It's not checked by /var/yp/Makefile.)

Do you have only one NIS master server or do you use slave servers? Is 'ypmatch john passwd' is executed on NIS client with correct NIS domainname set?

Please give me more details.

Comment 2 Ondrej Vasik 2011-02-22 14:54:50 UTC
In needinfo for more than 2 years and not reproducible on our machines - closing INSUFFICIENT_DATA. Feel free to provide more details about the system - but please do so only if you experience the issue with RHEL-5 or later and move that bugzilla there. RHEL-4.9 is now out and RHEL-4 updates now do contain only critical and security fixes.


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