From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2 Description of problem: In a patch submitted by a customer and applied as is, USE_BROADCAST was set to 0. It's normally set to 1 (from upstream) which makes ypbind do an RPC "ping" to all NIS servers at once and pick the first one that responds as the fastest. If USE_BROADCAST is set to 0, ypbind will try each of the servers in /etc/yp.conf in order, waiting for a timeout between them. Upstream has said this code hasn't been used or really tested in a long time. Additionally, it waits 60 seconds before trying the next server in the /etc/yp.conf file, which could lead to long time before a server is found to bind to if the first servers in the yp.conf file aren't responding. Version-Release number of selected component (if applicable): ypbind-1.12-5.21.1.src.rpm How reproducible: Always Steps to Reproduce: Run tcpdump or ethereal when starting the ypbind service Additional info: --- ypbind-mt-1.12/configure.bindings 2002-05-27 09:29:28.000000000 +0200 +++ ypbind-mt-1.12/configure 2004-09-20 15:15:48.061193257 +0200 @@ -5520,7 +5520,7 @@ echo "***" ;; linux*) - USE_BROADCAST=1 + USE_BROADCAST=0 echo "$as_me:$LINENO: checking wether we have glibc 2.1 or later" >&5 echo $ECHO_N "checking wether we have glibc 2.1 or later... $ECHO_C" >&6 cat >conftest.$ac_ext <<_ACEOF
I was unable to find a case where ypbind acted differently when USE_BROADCAST was changed from 0 to 1. I've removed the USE_BROADCAST section from the patch, but am unable to test what it fixed. It has been built into ypbind-1.12-5.21.6. An errata is also being filed.
Is an errata coming for this soon? This sort of change is really unnacceptable for anyone who has been using ypbind w/ Red Hat Linux for any length of time... especially after sweating a bunch of changes that were needed in the code that then got thrown out by this USE_BROADCAST change.
I believe that the fix will be in RHEL3U5. (The fix being USE_BROADCAST is reverted to its old setting, 1).
I don't see it in U5, which seems to be out now. What happened?
What is the version of the rpm you have? rpm -q ypbind.
Check out ypbind-1.11-broadcast.patch in ypbind-1.12-5.21.6.src.rpm
ypbind-1.12-5.21.1.src.rpm is the latest src.rpm in the RHEL3, and that's from 20-Sep-04.
This is in RHN and via up2date.
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-355.html
It appears that rhn didn't push out the latest rpms all at the same time. You should have recieve ypbind-1.12-5.21.6 from up2date by now. If not please re-open this bug.