Re: signal handling issues

Liste des GroupesRevenir à cu programmer 
Sujet : Re: signal handling issues
De : Muttley (at) *nospam* dastardlyhq.com
Groupes : comp.unix.programmer
Date : 02. Feb 2025, 10:45:47
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vnnesb$kkgs$1@dont-email.me>
References : 1 2 3 4 5
On Sat, 1 Feb 2025 22:06:29 -0000 (UTC)
Lawrence D'Oliveiro <ldo@nz.invalid> gabbled:
On Fri, 31 Jan 2025 09:15:39 -0000 (UTC), Muttley wrote:
>
All this confusion and complexity is why I always recommend that in a
multithreaded program if you must use signals then all signals should be
blocked with a single thread dedicated to sitting in sigwait() and handling
whatever comes along.
>
Or use signalfd(2) <https://manpages.debian.org/signalfd(2)>.

I never knew about that, very useful! Unfortunately it appears to be linux
only.


Date Sujet#  Auteur
30 Jan 25 * signal handling issues14Rainer Weikusat
30 Jan 25 +- Re: signal handling issues1Rainer Weikusat
30 Jan 25 +* Re: signal handling issues4Kaz Kylheku
30 Jan 25 i`* Re: signal handling issues3Dan Cross
31 Jan 25 i `* Re: signal handling issues2Rainer Weikusat
31 Jan 25 i  `- Re: signal handling issues1Dan Cross
30 Jan 25 +* Re: signal handling issues5Kaz Kylheku
31 Jan 25 i`* Re: signal handling issues4Muttley
1 Feb 25 i `* Re: signal handling issues3Lawrence D'Oliveiro
2 Feb 25 i  `* Re: signal handling issues2Muttley
4 Feb 25 i   `- Re: signal handling issues1Rainer Weikusat
3 Feb 25 `* Re: signal handling issues3Geoff Clare
6 Feb 25  `* Re: signal handling issues2Geoff Clare
6 Feb 25   `- Re: signal handling issues1Rainer Weikusat

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal