Make sure everything is up before starting message_bridge_client
The client wasn't reconnecting if the sender wasn't up. Work around
this for MTTD by waiting until everything is pingable
Change-Id: I211ba0966562d07e405e59afa0a568a694ffe2cf
Signed-off-by: Austin Schuh <austin.linux@gmail.com>
diff --git a/y2022/message_bridge_client.sh b/y2022/message_bridge_client.sh
index c81076a..733905e 100755
--- a/y2022/message_bridge_client.sh
+++ b/y2022/message_bridge_client.sh
@@ -5,7 +5,37 @@
ping -c 1 pi1 -W 1 && break;
sleep 1
done
+while true;
+do
+ ping -c 1 pi2 -W 1 && break;
+ sleep 1
+done
+while true;
+do
+ ping -c 1 pi3 -W 1 && break;
+ sleep 1
+done
+while true;
+do
+ ping -c 1 pi4 -W 1 && break;
+ sleep 1
+done
+while true;
+do
+ ping -c 1 pi5 -W 1 && break;
+ sleep 1
+done
+while true;
+do
+ ping -c 1 pi6 -W 1 && break;
+ sleep 1
+done
+while true;
+do
+ ping -c 1 roborio -W 1 && break;
+ sleep 1
+done
echo Pinged
-exec /home/admin/bin/message_bridge_client "$@"
+exec message_bridge_client "$@"