How to solve dependency conflict between initscripts at system start up in Red Hat Enterprise Linux?

Issue

• One daemon (say A) relies on another daemon (say B) for proper functioning. But the daemon B doesn't start before daemon A. We can workaround the problem by editing initscript for the daemons but what should be the sanest and cleanest method to achieve this.

• The following real world example involving quagga and snmp package in Red Hat Enterprise Linux (RHEL) 6 s can be used to illustrate this. The start up sequence of the zebra and bgpd daemons from the quagga rpm are ahead of the start up sequence of snmpd daemon. Zebra and bgpd depend on snmpd so theoretically snmpd should start up before them.
  The start up sequence in chkconfig is seen like this.

[user@blah init.d]$ grep chkconfig zebra bgpd snmpd
zebra:# chkconfig: - 15 85
bgpd:# chkconfig: - 16 84
snmpd:# chkconfig: - 50 50

• The problem shown above can also be workaround by editing the initscript in the source rpm of quagga. But often, quagga is started to set up network. Therefore, it doesn't make much sense to start SNMP before the network is fully initialized.