From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922 Description of problem: Red Hat NIS master does not send YP_NOMORE Attached are two PDFs that demonstrate the problem of when it works and when it doesn't. In both cases, the NIS client is Solaris 8 and the NIS Server is RedHat Enterprise Linux 3. The customer's recommended patch is attached as well. Version-Release number of selected component (if applicable): ypserv-2.8-9 How reproducible: Always Steps to Reproduce: Steps to Reproduce: 1. Setup Solaris & Linux Slave NIS servers. 2. Select a small nis map (such as auto.master) 3. Start packet sniffer when nis client is bound to Solaris ypserv 4. Perform 'ypcat auto.master' on client (or similar map) 5. Stop packet sniffer 6. rebind client to Linux box 7. Restart packet sniffer 8. Perform 'ypcat auto.master' again. 9. Stop sniffer 10. Compare the responses to 'yp_all' for the auto.master map 11. Notice the Linux one is missing the final record. Expected Results: Red Hat NIS Master should send YP_NOMORE Additional info:
Created attachment 105521 [details] expected results
Created attachment 105523 [details] failing results
Created attachment 105527 [details] customer's patch
fixed in ypserv-2.8-9
Chris, would you mind taking a look at this... I'm pretty sure I fixed this... tia
Where is the problem? Between the yp slave and the client, or the yp master and the yp slave? I don't see a YP_NOMORE in the .pdf which contains the expected results.
I've replicated the problem, fixed & tested the fix. Just waiting for verification from steved before commiting to the tree. This should appear in RHEL3U6.
This is fixed in ypserv-2.8-13 and should be in RHEL3U6.
Chris, Do you have an estimate on RHEL3U6 release. thanks, dave mahder
RHEL3 U6 is scheduled for release mid August.
A *test* version of the ypserv with the fixes is available at http://people.redhat.com/cfeist/ypserv/
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. http://rhn.redhat.com/errata/RHBA-2005-352.html