Hello
There is a second issue: wackamole runs "on top" of spread and starts
smoothly if spread is running at startup time. When spread dies (or is
being restarted), wackamole looses it's connection to spread, prints
out a message and keeps running happily without it. Needless to say
that it won't work any more.
Again, i have a suggestion: wackamole should immediately drop it's virtual
interfaces and then try to reconnect to spread, perhaps a few times. If
that fails, terminate.
I'm looking forward to see those changes in wackamole. I want to use it :-)
Regards,
Martin
There is a second issue: wackamole runs "on top" of spread and starts
smoothly if spread is running at startup time. When spread dies (or is
being restarted), wackamole looses it's connection to spread, prints
out a message and keeps running happily without it. Needless to say
that it won't work any more.
Again, i have a suggestion: wackamole should immediately drop it's virtual
interfaces and then try to reconnect to spread, perhaps a few times. If
that fails, terminate.
I'm looking forward to see those changes in wackamole. I want to use it :-)
Regards,
Martin