ypbind flips NIS servers constantly on every minute.

Solution Verified - Updated -

Issue

  • NIS server binding of Linux systems (run ypwhich to get the current binding) changes frequently. The man page for ypbind says that it checks the current server every 20 seconds to confirm it is up, and also pings all configured servers every 15 minutes to check on which is currently the fastest to respond. Red Hat added a patch to ypbind so that in debug mode it reports new and lost binding to a new server in verbose mode. It seems like “check all server” time is lowered from 15 minutes to 1 minute, presumably to speed things up when testing. This 1 minute forced-rebinding is still there. There should be no need to do a forced rebind every minute.

Environment

  • Red Hat Enterprise Linux 4
  • Red Hat Enterprise Linux 5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content