Indeex, I used the numbers from RH6. Yeah, min/max change based on the
distro, sigh. Anyway, some thread is unblocking these signals.

On Wed, 15 Jan 2020, Matev? Tadel wrote:

> Xrootd does not use SIG 64 and SIG 63, it uses SIGRTMAX and SIGRTMAX - 1 :)
>
> On fedora 30 these are:```
> root [2] SIGRTMIN -> (int) 34
> root [3] SIGRTMAX ->(int) 64
> root [4] SIGRTMAX - SIGRTMIN -> (int) 30
> ```
> so `SIGRTMAX - 1 = SIGRTMIN + 29`.
>
> How about a plugin using signals and not blocking the RT signals (or unblocking them through ignorance) so they get delivered there from XRootd AIO code, even though they should not? Although I must admit I can not imagine the mess when signals are used for internal communication by two different sub-systems in a single multi-threaded program :)
>
>
>
> --
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1113#issuecomment-574859815


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1113?email_source=notifications\u0026email_token=AA7NRDUYYA7FFNDPCXXGM53Q554UBA5CNFSM4KG2BO5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJB23IA#issuecomment-574860704", "url": "https://github.com/xrootd/xrootd/issues/1113?email_source=notifications\u0026email_token=AA7NRDUYYA7FFNDPCXXGM53Q554UBA5CNFSM4KG2BO5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJB23IA#issuecomment-574860704", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1