Print

---

So, the solution is not very straightforward

What's wrong with this:

 struct XrdXrootdMonFileLFN
      {
       kXR_unt32           user;     // dictid for the user
       char                lfn[1032];// Variable length, nul-terminated.
      };

 struct XrdXrootdMonReqAuth
      {
       char                authinfo[1032]; // Variable length, nul-terminated,
                                           // similar to authinfo in the `u` record but remove
                                           // connection-specific items like hostname or appinfo.
      };

struct XrdXrootdMonFileOPN
      {
       XrdXrootdMonFileHdr Hdr;      // recType == isOpen
       long long           fsz;      // file size at open
       XrdXrootdMonFileLFN ufn;      // OPTIONAL, present if recFlag & hasLFN is set.
       XrdXrootdMonReqAuth authn;    // OPTIONAL, present if recFlag & hasAuth is set.
       };

Fortunately, we have a couple of years to figure this out and I am sure we will

I'm not sure why there's a couple of years here. Most of the authenticated data in OSDF uses tokens. Isn't ~99% of the LHC WAN data moved using macaroons (and hence missing f-stream data) as well?

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/1987/1496392225@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