 |
 |
OK, I looked at the code and technically it is doing the right thing and handling kXR_waitresp in the expected way. Why the http thread is not resuming is mysterious as it should be. Anyway of running a checksum calc with full debugging turned on so we can see if here is something special going on in the checksum code path when the checksum has to be calculated? Should that not provide sufficient info, is there a setup I can get to for a gdb session? Andy On Fri, 8 Feb 2019, Fabrizio Furano wrote: > Hi Brian, > > well, I agree that they are async, yet if the request came from XrdBridge then > also the response has to come through XrdBridge. I consider this a bug of > the core. > > I'd like to have Andy's opinion on this. > > About the login name... that's history. I remember I needed just to fill that > field with something that is somehow human readable. What would you put there? Some > CN number? > > f > > > > -- > You are receiving this because you commented. > Reply to this email directly or view it on GitHub: > https://github.com/xrootd/xrootd/pull/902#issuecomment-461736230 > > ######################################################################## > 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 ######################################################################## 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