>> - early stop?
>>  testing/pluto/klips-netkey-pluto-06 failed east:output-different
>> west:output-different
> if final.sh runs a status or trafficstatus and also shuts down pluto for
> a leak report, there is a race between nodes. If one shuts down fast,
> the other won't see the proper status because it will have processed the
> deletes from the other peer's shutdown. The rule is to not have status
> and shutdown in final.sh.

This one is a no win.  We've too often missed core dumps because pluto
wasn't being shutdown.

What about wrapping the inconsistent output in --cut-- --tuc--?

Swan-dev mailing list

Reply via email to