Indeed, linking against Globus usually (though not always) screws up
signal handling. That has been an ongoing problem for at least two decades
now. They fix it then break it again and again.
On Fri, 17 Jan 2020, Brian P Bockelman wrote:
> @bockjoo - does the problem go away if you turn off asynchronous IO? That is, try adding:
> ```
> xrootd.async off
> ```
>
> Has this been ongoing for awhile or is it something new?
>
> I suspect it's probably due to the fact that `XrdLcmaps` links against Globus to do the proxy verification and that is somewhere causing Globus to try and take over signal handlers. Nothing else I know of besides Globus would touch that from a plug-in point-of-view.
>
> --
> 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-575599443
—
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=AA7NRDSUKPHNP42ULDYJJ3DQ6IKUVA5CNFSM4KG2BO5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJI5VMQ#issuecomment-575789746",
"url": "https://github.com/xrootd/xrootd/issues/1113?email_source=notifications\u0026email_token=AA7NRDSUKPHNP42ULDYJJ3DQ6IKUVA5CNFSM4KG2BO5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJI5VMQ#issuecomment-575789746",
"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
