Hi Scott,
In case it wasn’t obvious: Starting IOCs inside tmux or procServ (or GNU Screen as we use at APS) is recommended to allow you to connect to the IOC console and run diagnostic commands using the IOC shell, in case you need to debug issues with
the IOC or its client connections. It is possible to create and run IOCs without a shell, but it provides many commands which can give you information about what it’s doing which you can’t otherwise access remotely.
The procServ package is probably the simplest approach, but it doesn’t give you the ability to scroll back and look at messages that were shown on the IOC console before you connected, like tmux or Screen can. You can have procServ log the console
output to a file though, or if you start it using systemd it could send everything to the systemd journal.
Recent versions of procServ come with support scripts for use with systemd; post here if you have questions about them.
HTH,
- Andrew
Hi Lewis and Ernesto,
Thank you both for the advice! I appreciate your support and will try out both approaches.
Best,
Scott
-----Original Message-----
From: J. Lewis Muir < jlmuir at imca-cat.org>
Sent: Tuesday, July 20, 2021 7:24 PM
To: Feister, Scott < scott.feister at csuci.edu>
Cc: tech-talk at aps.anl.gov
Subject: Re: Best practices for booting IOC at Linux startup?
CAUTION: This email originated from outside of CSUCI. Do not click links or open attachments unless you validate the sender and know the content is safe. Contact ITS if you have any concerns
On 07/20, Feister, Scott via Tech-talk wrote:
Can anyone share some best practices on having an IOC boot whenever Linux boots? I'm trying to make it as easy as possible to reboot the instrument, by simply power cycling. The hardware is a Raspberry Pi whose sole purpose
is to boot and run its IOC every time it powers on. Thanks!
I run my soft IOCs in tmux started as a service.
Lewis
--
Complexity comes for free, simplicity you have to work for.
|