On 7/22/13 1:12 PM, Andy wrote:
I messed up and added '!sleep 5' to the hostname.carp instead of the
physical interface..
None the less I'm surprised that no one else has any thoughts on this
when it has been discussed several times before.
It would be /very/ easy to resolve (by someone with talent and
experience of the code base ;) and would aid the stability of OpenBSD
greatly (in an operational sense), as the knock on effects this has
really affect sasyncd, openbgpd and openospfd to name to the ones I have
problems with when a cable is pulled/NIC reset etc.
E.g. https://groups.google.com/forum/#!topic/fa.openbsd.tech/NXy2rivB_z0
I feel your pain. ;-) (the mail in the link is mine)
I cannot imagine their is a technical challenge beyond adding a sleep(x)
at INIT state with 'x' taken from a sysctl value (saying this as someone
who doesn't know the code base at all). - One day when I have more time
I will check it out..
If you happen to have the code base nearby I would really appreciate so
much if you could throw a sleep in after CARP moves to INIT.
Adding a sleep is simple indeed, but then everything would stop for x
seconds...
Seriously, I tried and found it hard to add. The carp functionality is
event/timer based and there are already mechanisms in there that
suppress and/or delay.
--
Cam
