7.239. ypbind

Bug Fixes

BZ#829487

Previously, the localhost was not treated specifically in the domains list of the ypbind program. Consequently, when the network connection was not established the ypbind did not bind to the ypserv utility on the localhost. With this update, a check for the localhost has been added, and now ypbind works even if the network connection is off.

BZ#842228

Prior to this update, the SIGPIPE signal was not in the proper signal set. Consequently, when a loss of network connectivity occurred, the ypbind utility terminated unexpectedly. Adding SIGPIPE to the proper signal set fixes this bug, and ypbind no longer crashes.

BZ#888778

Previously, the ypbind program's init script did not check for the presence of the ypbind line in the /etc/rpc file. As a consequence, if the ypbind line was not present, ypbind failed to start. This update adds a patch to check for the presence of the ypbind line in /etc/rpc. As a result, ypbind provides a warning message in the log files when its line is missing in /etc/rpc.

Enhancement

BZ#918276

This update adds a configurable option for setting the time interval which is used by the ypbind program to retry rebinding. Previously, ypbind checked for the fastest NIS server every 15 minutes. This in some cases led to intermittent failures when the default timeout interval on a server firewall was set to 10 minutes. The added configurable option allows to set a specific time interval after which ypbind performs a check for the fastest NIS server, and thus avoids the intermittent failures during the rebinding process.