On Thu, Apr 10, 2008 at 2:33 PM, Stuart Henderson  wrote:

quoted text
>  Problem is, a carp interface is not interested in the state of the

>  syncdev, it is interested in the state of its own carpdev (since

>  multiple carp interfaces on a machine are independent). And carpdev

>  usually faces a switch, so it stays up.

I didn't mean it would monitor the state of its own carpdev, but that

you'd be able to set an extra watchdev (or whatever) that it would

watch.