 |
 |
Well, it's somewhat the case that `xrootd.trace auth` spits it out. This is what I get back from a GSI connection: ``` 220718 21:02:37 68759 sysThrottleManager: Current IO counter is 0; total IO wait time is 601ms. 220718 21:02:37 69034 root.231196:[log in to unmask] Xrootd_Protocol: more auth requested; sz=3353 root.231196:[log in to unmask] Protocol 'gsi' root.231196:[log in to unmask] Name 'cmsprod' root.231196:[log in to unmask] Host 'cmsrucioprod1-la5qxltcbmcu-node-3.ipv6.cern.ch' root.231196:[log in to unmask] Vorg 'cms cms' root.231196:[log in to unmask] Role 'production NULL' root.231196:[log in to unmask] Grps '/cms /cms' root.231196:[log in to unmask] Caps '' root.231196:[log in to unmask] Pidn 'root.231196:[log in to unmask] root.231196:[log in to unmask] Crlen 0 root.231196:[log in to unmask] ueid 172 root.231196:[log in to unmask] uid 0 root.231196:[log in to unmask] gid 0 ``` ... first off, none of this is the DN, so it's not at all what I could use to find a user, much less to ban them. Secondly (and more minorly), this apparently comes through some other subsystem with a different logging facility, so the latter logs don't have the threadID with them letting you disambugate who is reading what file. Thanks! -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1738#issuecomment-1188517632 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