[Spread-users] Spread startup

[Ian Eiloart]

Hi,

I have spread configured with this segment only:
Spread_Segment 139.184.15.255:4803 {
        karpinski       139.184.14.85
        chip            139.184.14.86
        lynndie         139.184.14.87
        sivits          139.184.14.88
}

I'm using wackamole, configured to share about 20 IP addresses in virtual 
interfaces ("VIFs") between those four
machines. Sometimes, when I use wackatrl -l, I get output like this:

Owner: 127.0.0.1
        *     lo0:139.184.14.101/32
         ->   lo0:139.184.14.70/32

Implying that the loopback interface (on some host) has control of one of
my VIFs. My guess is that this happens because spread and/or wackamole are
starting before en0 is up.

It seems to me that this is probably an issue with spread - it shouldn't
really start before the hosts native interfaces are configured, should it? 
Or is
there some configuration option in spread or wackamole that I'm missing.

My proposed solution (using launchd on OSX, which doesn't let me specify
launch order or dependencies) is to start a script (instead of spread)
which waits for en0 to come up, then execs spread.
-- 
Ian Eiloart
IT Services, University of Sussex