Restart sysrepod, netopeer2-server and the cla-sysrepod upon failures
In addition, a restart of sysrepod is bad enough so that it restarts
everything else, and a failed netopeer2-server results in a restart of
sysrepod (and therefore everything else) because there's quite some
potential for confusion otherwise.
I saw that confusion; it wasn't pretty.
Change-Id: Iba18f594014c70e94727b69cd81ac9c57a0eafdb
diff --git a/board/czechlight/common/overlay/etc/systemd/system/czechlight-roadm-v2.service b/board/czechlight/common/overlay/etc/systemd/system/czechlight-roadm-v2.service
new file mode 100644
index 0000000..3afd902
--- /dev/null
+++ b/board/czechlight/common/overlay/etc/systemd/system/czechlight-roadm-v2.service
@@ -0,0 +1,19 @@
+[Unit]
+Description=CzechLight CL-ROADMv2 driver
+After=syslog.target network.target sysrepod.service
+Reuires=sysrepod.service
+PartOf=sysrepod.service
+
+[Service]
+Type=simple
+ExecStart=/usr/bin/cla-sysrepod --properties-log-level=5 --sr-bridge-log-level=5 --sysrepo-log-level=3 --driver=CL-ROADMv2 --port=/dev/ttyUSB0
+PrivateTmp=yes
+PrivateDevices=no
+ProtectSystem=yes
+ProtectHome=yes
+SystemCallArchitectures=native
+Restart=always
+StartLimitIntervalSec=0
+
+[Install]
+WantedBy=multi-user.target