Bug 680351 - ypbind checks for fastest server every minute (should be 15 minutes)
Summary: ypbind checks for fastest server every minute (should be 15 minutes)
Status: CLOSED DUPLICATE of bug 594670
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: ypbind
Version: 4.8
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Karel Klíč
QA Contact: qe-baseos-daemons
Depends On:
TreeView+ depends on / blocked
Reported: 2011-02-25 08:28 UTC by Masahiro Matsuya
Modified: 2013-03-03 23:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-02-25 08:32:13 UTC

Attachments (Terms of Use)

Description Masahiro Matsuya 2011-02-25 08:28:05 UTC
Description of problem:
ypbind will check to see if the current NIS server is the fastest every 1 minite.
But, manpage of ypbind says it's 15 minites.

This occurred with a fix of https://bugzilla.redhat.com/show_bug.cgi?id=198689.
The fix includes this part:

@@ -1024,7 +1049,8 @@ test_bindings (void *param __attribute__
 	pthread_exit (&success);
       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);

So, it was changed into 60 second (1min) clearly here. But, I cannot see why this change is needed for the fix of BZ198689. 

The fix on BZ198689 was introduced from rhel4.5. So, this can be a regression from rhel4.4 or before.

Version-Release number of selected component (if applicable):
ypbind-1.17.2-13 and later

How reproducible:

Steps to Reproduce:
1. run ypbind 
2. check the interval of "Pinging all active server" message
Actual results:
ypbind checks it every 1 min

Expected results:
ypbind checks it every 15 min

Additional info:

RHEL5 has this same change, which means the same bug.
RHEL6 doesn't have this change.

Comment 2 Masahiro Matsuya 2011-02-25 08:32:13 UTC
This is duplicate of BZ594670. Sorry for noise.

*** This bug has been marked as a duplicate of bug 594670 ***

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