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/netopeer2-server.service b/board/czechlight/common/overlay/etc/systemd/system/netopeer2-server.service
new file mode 100644
index 0000000..850c5b5
--- /dev/null
+++ b/board/czechlight/common/overlay/etc/systemd/system/netopeer2-server.service
@@ -0,0 +1,20 @@
+[Unit]
+Description=A NETCONF server on top of sysrepo
+After=syslog.target network.target sysrepod.service
+Requires=sysrepod.service
+PartOf=sysrepod.service
+
+[Service]
+Type=forking
+ExecStart=/usr/bin/netopeer2-server
+PIDFile=/var/run/netopeer2-server.pid
+PrivateTmp=yes
+PrivateDevices=yes
+ProtectSystem=yes
+ProtectHome=yes
+SystemCallArchitectures=native
+Restart=always
+StartLimitIntervalSec=0
+
+[Install]
+WantedBy=multi-user.target