Re: Segfault when running wackamole in foreground

Hi!  I don't know about why Wackamole is segfaulting, although I'll look 
into it if it continues as a problem for you.  My concern is that your 
spread.conf seems incorrect, which might cause wackamole to behave in an 
odd manner.

The sample.spread.conf often causes confusion about this, but a 
localhost segment should only be included in the configuration if its 
the only segment (which only makes sense if you're using only one 
machine).  The second segment, which should be the only one as far as I 
understand your configuration, doesn't have a broadcast or multicast 
address, but rather the address of one of the two hosts.  I'm not sure 
what Spread's response to this would be, but it might run and simply try 
to communicate.  You should replace the address with either the 
broadcast address 192.168.0.255, or a multicast address (in the range 
224.0.0.0 through 239.255.255.255, excluding some reserved addresses).

> My spread.conf looks like this:
> 
>    Spread_Segment 127.0.0.255:4803 {
>         localhost               127.0.0.1
>    }
>  
>    Spread_Segment 192.168.0.253:4803 {
>         factotum                192.168.0.253
>         cc                      192.168.0.1
>    }
> 

On a side note, you might want to change this when you stop using 
Wackamole only for tests.  There should be discussions on the subject in 
the list archives.

>   mature = 5s

Good luck,
Ryan

-- 
Ryan W. Caudy
Center for Networking and Distributed Systems
Department of Computer Science
Johns Hopkins University