Add the same mechanism I developed for the SwSS service in #2845 to the syncd service. However, in order to cause the SwSS service to also exit and restart in this situation, I developed a docker-wait-any program which the SwSS service uses to wait for either the swss or syncd containers to exit. |
||
---|---|---|
.. | ||
bfn-modules | ||
docker-saiserver-bfn | ||
docker-syncd-bfn | ||
docker-syncd-bfn-rpc | ||
sonic-platform-modules-arista@10750325b6 | ||
sonic-platform-modules-bfn | ||
sonic-platform-modules-bfn-montara | ||
sonic-platform-modules-bfn-newport | ||
sonic-platform-modules-ingrasys | ||
sonic-platform-modules-wnc-osw1800 | ||
bfn-modules.mk | ||
bfn-platform-ingrasys.mk | ||
bfn-platform-wnc.mk | ||
bfn-platform.mk | ||
bfn-sai.mk | ||
docker-ptf-bfn.mk | ||
docker-syncd-bfn-rpc.mk | ||
docker-syncd-bfn.mk | ||
libsaithrift-dev.mk | ||
one-aboot.mk | ||
one-image.mk | ||
platform-modules-arista.mk | ||
platform-modules-bfn-montara.mk | ||
platform-modules-bfn-newport.mk | ||
platform-modules-bfn.mk | ||
platform-modules-ingrasys.mk | ||
platform-modules-wnc-osw1800.mk | ||
platform.conf | ||
rules.mk |