OMSHELL to Reload Host Config File or cpan Net::ISC::DHCPd::OMAPI Examples

[J Springer]

David W. Hankins wrote:
> if you are making config from an oft-refreshed file as a source, i'd
> just recommend restarting dhcpd on a new config file rather than using
> omapi to manage changes.  the brief time to restart the daemon will
> pass unnoticed, whereas the omapi-managed method presents a lot of
> moving parts and complex machinery that can just go wrong.

This is what we're doing in a non-failover environment due to the regularity of 
host adds, changes and deletes that occur during the day (low volume).

However, we're moving to a failover server pair.  Is it common practice to use 
omapi for host changes or would we be better served with a short mclt relative 
to the delta between server restarts?

What is your recommendation?