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

[Érico Nogueira Rolim via Tech-talk <tech-talk at aps.anl.gov>]

On 03/04/2025 10:17, Ralph Lange via Tech-talk wrote:
> Another attempt to summarize...
>
> 1. You want EPICS Base to provide - on demand, after calling a
> function - an extra thread that waits on a specific exitEvent and
> calls epicsExit when it receives it.
>
> I'm generally fine with that, given that this is portable,
> lightweight, and doesn't add anything if you don't call the function.
> To not expose the event mechanism, I would add another function
> wrapping around sending exitEvent.


Given the existence of epicsExitLater, it might even be possible to
share part of the implementation with it. And for sure, no direct usage
of the event!


>
> 2. You want EPICS Base to install signal handlers for an arbitrary
> number of signals, which send the exitEvent when they get called.
>
> For me, this is the more problematic part. Not portable, possible side
> effects.
>
> Could Base implement the first part (exit-on-event), and the second
> part (signal handlers) be left to a separate module? Such a module
> could provide implementations for Windows and Linux and be a lot more
> flexible, with a lifecycle that is not bound to EPICS Base.


That would seem reasonable to me. Is that your recommendation for moving
this forward?


>
> Cheers,
> ~Ralph



Aviso Legal: Esta mensagem e seus anexos podem conter informações confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo e considere eventual consulta ao remetente antes de copiá-la, divulgá-la ou distribuí-la. Se você recebeu esta mensagem por engano, por favor avise o remetente e apague-a imediatamente.

Disclaimer: This email and its attachments may contain confidential and/or privileged information. Observe its content carefully and consider possible querying to the sender before copying, disclosing or distributing it. If you have received this email by mistake, please notify the sender and delete it immediately.