Re: RFC: add a mechanism to call epicsExit when signals are received

[Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov>]

On 6/26/26 10:30 AM, Érico Nogueira Rolim via Tech-talk wrote:

Any thoughts or updates on Linux signalling for EPICS from the devs?

I don't think there have been any updates, but I remember there were implementation suggestions for my idea. For epics-base, it would consist of launching a thread listening on an epicsEvent, which, when signaled, would call epicsExit. For a module with platform specific code, it would consist of registering signal handlers (possibly automatically or via iocsh commands) and having those signal the previously mentioned epicsEvent.

If you're keen on getting your hands a little dirty, how about we collaborate on moving this forward? Maybe start implementing the epics-base interface so we can check its suitability for the support module?

As far as APIs.  If epicsAtExit() is not enough, or if the ordering gets too complex, I would suggest looking at the "de-init" hooks.  See "initHookAtShutdown" in initHooks.h .

also fyi. https://github.com/epics-base/epics-base/pull/673