[Ace] caRepeater on RHEL 9

Anthony Cuffe cuffe at jlab.org
Thu Sep 8 15:45:44 EDT 2022


In the past, we have relied on caRepeater always being in the path of the first person to do something epics related.  On some systems we deliberately starting it from an init script.  For RHEL 9, I wanted to solve this problem more globally.  I created an RPM for just caRepeater that installs in in /usr/bin and creates a system startup script for it (similar to the old /etc/init.d scripts).  The system daemon will watch the process and restart it if it dies.

Does anyone have any issues with this occurring on all systems by default?  We could remove the rpm on systems where this might cause some sort of problem.

This is only for RHEL 9 unless it works so well everyone wants me to back-port it.

Here is the RPM information.

Name        : ace-caRepeater
Version     : 3.15.9
Release     : 1.el9
Architecture: x86_64
Install Date: (not installed)
Group       : System Environment/Base
Size        : 239415
License     : GPL
Signature   : (none)
Source RPM  : ace-caRepeater-3.15.9-1.el9.src.rpm
Build Date  : Thu 08 Sep 2022 01:31:01 PM EDT
Build Host  : localhost
Packager    : Anthony Cuffe <cuffe at jlab.org>
Summary     : caRepeater and systemd service (epics 3.15.9)
Description :
Local epics caRepeater binary and systemd service.  This ensures
that a caRepeater process is started at boot time.  It was built
with epics 3.15.9
/etc/systemd/system/caRepeater.service
/usr/bin/caRepeater
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/ace/attachments/20220908/e3b07fb1/attachment.html>


More information about the ace mailing list