On 4/3/13 3:54 PM, Stuart Henderson wrote:
On 2013/04/03 15:43, Camiel Dobbelaar wrote:
On 4/3/13 3:34 PM, Stuart Henderson wrote:
In some cases when a network port comes up, it does not indicate that
the network is ready. But on linkup, carp(4) will try to get out of
the INIT state as soon as possible. And because all is quiet it will
decide to become master.
Anyone else observe/fix this by other means? Opinions?
slightly messy, though at least this also applies to the case with
things other than carp which could also have problems: add "!sleep 5"
or something in hostname.if for the physical interface...
Yes, I already use that. That solves the case where the system with
the carp interfaces itself is rebooted.
But not the other cases. Hence I'd like that sleep applied always,
instead of only when /etc/netstart is run. :-)
Ah, I see what you mean. Still there are things other than carp
where this might also apply - for example the pfsync initial_bulk
that gets handled via if_linkstatehooks (but maybe also userland
things)..
Pausing carp may help the pfsync case too?
Wasn't the major problem there caused by the freshly booted backup going
to master too soon and cancelling the bulk update?
