Peter N. M. Hansteen wrote:
"Denis Doroshenko" <[EMAIL PROTECTED]> writes:
what keeps you from writing a script that would be called
from the end of /etc/netstart; the script would check whether the
initialized network interfaces match those described by a
predefined table? in case of failure it would react somehow...
Then again, given the 'failure is not an option' scenario, any sane
network design would mean you most likely have a multiply redundant
CARP'd setup in place, so a hardware failure like the one described on
one box would simply mean the machine would take itself out of the
running, one of the backups would take over and your friendly robot
helper would be paging you to replace the failed hardware at your
earliest opportunity.
By all means nothing stops you from writing script magic, but the
tools already in your OpenBSD base system lets you solve these
situations quite admirably and in several differen ways already.
If you actually require fault tolerance, this is the best advice so far.
Your devices are ordered as you expect them to be, your rule base is in
a known good state. The system uses supported features making upgrades
simple, as well as leaving off the sort of site specific quirks that can
make inheriting a site so challenging.
