Bug 1027617

Description of problem:
The init script of ypbind starts before ypserv. If the same host is
the only available NIS server, ypbind is killed again, before
ypserv is started, what works without problem. This problem arises,
when for instance
* the host itself is the only available NIS server e.g. because
  others are not available e.g. not (yet) up e.g. when all NIS
  servers are booting at the same time
* the host should be the only NIS server for itself (standalone
  configuration while nameservice data updates)

Version-Release number of selected component (if applicable):
ypbind-1.20.4-30.el6.x86_64
ypserv-2.19-26.el6.x86_64


How reproducible:
On a NIS server, only add the same host or localhost in
/etc/yp.conf and reboot. ypbind will fail to start (the init
script checks, whether the NIS service is bound and timeouts
after several attempts and kills ypbind), because ypserv is
not yet available. ypserv will happily start later.

Steps to Reproduce:
1. Set up a working NIS server, assume domain name "localdomain"
2. make this the first line in /etc/yp.conf: domain localdomain server localhost
3. reboot

Actual results:
NIS not bound, no nameservice data from NIS available

Expected results:
NIS is bound, the local ypserv is queried, nameservice data from NIS available

Additional info:
ypbind is started in /etc/rc5.d/S24ypbind ,
ypserv in /etc/rc5.d/S26ypserv . I changed that to
/etc/rc5.d/S25ypbind and /etc/rc5.d/S24ypserv and
it works for me, though i do not consider this a
clean solution. ypserv should start after network
i.e. S24 . ypbind should start after ypserv i.e. S25
but other programs started in S24 and S25 might already
need nameservice data from NIS, so everything in S24
should move up at least by 2 and all stuff above likewise.