Hi Greg,
I know the instructions in systemd-softioc seem too long (too long; didn't read). I will try to simplify ‘README’ as much as possible.
There is one sentence you probably did not pay enough attention: “CHDIR/EXEC: if you do not have st.cmd in /epics/iocs/example1, you have to set CHDIR and EXEC accordingly. See config.example for reference.”. So you just need to add one more variable “CHDIR=/epics/iocs/myIOCname/iocBoot/iocmyIOCname”.
Cheers,
Yong
This looks slick, but I don’t quite understand how to set it up. I ran through the instructions, got procServ installed (still not in EPEL for Centos 9), got system-softioc installed, created /epics/iocs and made the config file, and then
got confused. It says that st.cmd should be in that directory, but st.cmd as generated (I think by makeBaseApp.pl) contains a lot of relative paths. Does that mean that my whole IOC should have been created in /epics/iocs/myIOCname? If I do that, my st.cmd
will wind up in /epics/iocs/myIOCname/iocBoot/iocmyIOCname/. That doesn’t match with the default path that shows up in the output of ‘manage-iocs report’, which makes me feel like I’ve missed some steps.
I also found that procServ won’t work with the python that ships with Centos 9 Stream, unless I pulled the change from commit 3330d41 (which apparently landed 6 weeks after the last tarball was made in 2019).
Greg
--
Gregory Leblanc
Accelerator Engineer
Edwards Accelerator Lab - Ohio University
123 University Terrace
Athens, OH 45701 USA
[email protected]
M: (401) 52-OUAL1 or (401) 526-8251
On Tue, 20 Jun 2023 at 16:26, David A. Slimmer via Tech-talk <[email protected]> wrote:
I’m trying to setup a pi node so that it starts my IOC at boot time using systemd. [...]
Many facilities use procServ to run IOCs, which also provides access to the IOC console.
procServ is known to be handling systemd starting nicely.