Re: loopback

--On 28 September 2006 09:14:11 -0400 Theo Schlossnagle <[email protected]> 
wrote:


>
> Wackamole requires a few things to be configured/running when it is
> started:
>
> o IP networking and static IPs with established routes on the  interfaces
> that will host the VIFs.
> o It's hostname to be set and the IP address to which that resolves
> (gethostbyname) should be an identifying IP address (not 127.0.0.1)
> o Spread must be running.
>
> Wackamole doesn't ship with startup scripts for Mac OS X, so you are  on
> your own to implement the startup procedure and satsisfy the above
> requirements.
>
> It's worth noting that I think the issue is that the hostname is
> referring to localhost (or at least resolving there) when wackamole
> starts which means host level networking has not yet been completely
> configured and you are trying to start a networked service that needs  it.
>

That sounds about right. What I'm planning on doing is writing a wrapper 
script that will wait until an interface other than lo0 is available, then 
exec wackamole. This will allow me to use OSX's launchd, which has no way 
of specifying dependencies when launching daemons. Launchd expects daemons 
to be robust to missing dependencies.

My rough plan is to check for a useful interface every second, up to some 
timeout period.

I don't know if spread lets you ask what the Spread_Segment members are, 
but if it does, then it would be a neat for wackamole to ask for the IP 
addresses in the segment, and wait until it has local access to one of 
those IP addresses before proceeding. Otherwise, it could at least wait 
until it has access to an interface that isn't lo0.


-- 
Ian Eiloart
IT Services, University of Sussex