Experimental Physics and
| |||||||||||||||
|
Hi all, The only way of starting an IOC I have learned is by running the `st.cmd` script, which by default opens an iocsh shell on success. I am seeing 2 problems when running IOCs in containers: 1. The iocsh shell seems redundant as nobody will actually use it when run in containers. A way to start IOC which does not open up iocsh is a more light-weight solution. 2. When running an IOC container with `-d` option only, the container stops immediately. A dirty workaround is using `-it` option to attach a pseudo-tty to the container. The caveat is that when the IOC is broken the container keeps running. Although a liveliness probe can be used to check the health condition of the IOC, a container exiting when the IOC is broken is certainly a more light-weight and reliable solution. TL;DR, is there a proper way to start a persistent iocsh-less IOC instance?
| ||||||||||||||
ANJ, 15 Jun 2020 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |