seesaw_engine triggers os.Exit. This is common whenever
log.Fatal/Exit is called.
SIGTERM is received.
In both cases seesaw_ha may still keep announcing as master
which causes traffic disruption.
This commit fixes this by watching seesaw engine socket file in
seesaw_ha:
os.Exit doesn't clean up so engine socket file is not removed. But
all ipvs services keep working until a new seesaw_engine instance wipes
out previous config. So we remove leftover engine socket file first
thing to exit seesaw_ha before wipe out.
SIGTERM will be handled gracefully and engine socket is removed
before exiting. seesaw_ha will notice the deletion and exit together.
seesaw_engine may exits in two cases:
In both cases seesaw_ha may still keep announcing as master which causes traffic disruption.
This commit fixes this by watching seesaw engine socket file in seesaw_ha: