Added systemd service specification to work around problem, see README file.

misc/README

+----NOTICE----
+The lebt emu has an unclear/unidentified issue with running as ioc user. 
+However a hint may be that a different database behavior was observed when it comes to the signalling of that all detector finished in scanDAQDetTrig.template from scanning module.
+This seems to only occur when running as ioc user. The effect is that the scan hangs because the counter record: $(DEVICE):$(DETTRG)-DETCNT in scanDAQDetTrig.template is incremented incorrectly, maybe due to abundant or insufficient number of processing for each point in the inner scan.
+
+The work around is to run the ioc as root user. A special systemd service has been constructed to this without interferring with standard ioc booting procedure.
+
+The systemd service specification should be placed in the root file system under /etc/systemd/system/
+
+To reload systemd services run: systemctl daemon-reload
+To start the ioc: systemctl start emu-lebt

misc/emu-lebt.service

+[Unit]
+Description=IOC: emu-lebt
+After=rc-local.service
+ 
+[Service]
+User=root
+ 
+# Only execute IOC if st.cmd exists
+AssertPathExists=/opt/startup/ioc/VME_EMU-iamspecial/emu/st.cmd
+ 
+# Execute StartPre with root permissions
+ExecStartPre=/bin/mkdir -p /var/log/procServ
+ExecStartPre=/bin/chown -R ioc:ioc /var/log/procServ
+ExecStartPre=/bin/mkdir -p /var/run/procServ/emu
+ExecStartPre=/bin/chown -R ioc:ioc /var/run/procServ/emu
+EnvironmentFile=/opt/startup/ioc/VME_EMU-iamspecial/emu/env.sh
+ 
+# Run procServ with user ioc
+ExecStart=/usr/bin/procServ --allow -f -L /var/log/procServ/out-emu -i ^C^D -c /var/run/procServ/%i ${PROCSERV_PORT} ${EPICS_MODULES_PATH}/environment/${ENVIRONMENT_VERSION}/${BASE}/bin/${EPICS_HOST_ARCH}/iocsh /opt/startup/ioc/VME_EMU-iamspecial/%i/st.cmd -n emu