Print

Print


Well, you promised it would not be called again :) The first time around, if Pfc needs more time, it will keep scheduling a job to check if IO is active and then call detach-finalize and invoke the CB you passed into original Detach. If you call detach again it will redo the ioactive check and potentially do what the scheduled job is supposed to do ... and the scheduled job will then land on a deleted object. So, nothing good.

What do you expect to happen to the CB you've passed in to the first / original Detach?

Why would you actually need to call Detach multiple times? You told me that when you call detach on your side the posix object is as good as gone so if a new request comes for the same file a new posix object will be created.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/pull/1724#issuecomment-1160941708
You are receiving this because you are subscribed to this thread.

Message ID: <[log in to unmask]>

########################################################################
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