+++ This bug was initially created as a clone of Bug #594668 +++
Description of problem:
The ypbind manual page says that it checks the current server every 20s to confirm it is up, and also pings all configured servers every 15 minutes to check on which is currently the fastest to respond. In fact it pings the servers every minute which may cause ypbind to flip the servers very often.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. configure ypbind to try to contact more servers, i.e. add two servers to /etc/yp.conf (one of them must be reachable):
2. start ypbind in the debug mode
3. it logs out the pings of the servers
The "Check new for fastest server." logs appear every minute:
The "Check new for fastest server" logs appear every 15 minutes (as documented)
This seems to be caused by the ypbind-mt-1.17-log-binds.patch which contains the following chunk:
@@ -1024,7 +1049,8 @@ test_bindings (void *param __attribute__
lastcheck += ping_interval;
- if (lastcheck >= 900) /* 900 = 15min. */
+ //if (lastcheck >= 900) /* 900 = 15min. */
+ if (lastcheck >= 60) /* 900 = 15min. */
lastcheck = 0;
lastcheck = test_bindings_once(lastcheck);
At the first glance it looks like this has been added for the debugging purposes to test the patch for the bug #198689. We should revert this part or explain why does the interval have to be shortened this much and fix the documentation.
Yes, the limit should be set back to 900 (15 minutes).
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
*** Bug 680351 has been marked as a duplicate of this bug. ***
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 therefore 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.