Print

Print

I am not sure what you mean by thread ID here as threads get reassigned as needed and are not meaningful over the life of a session. The more meaningful is root.231196:[log in to unmask] where you see the host name and 231196:70 is the process ID of the client running on that host. That won't change during the whole session. I agree that you really don't get enough info here to ID the user (well there was hope), especially since lcmaps (or whatever mapping being used) mapped the user to cmsprod (which makes sense). But who is that? Well, who knows. Maybe I can conjure something up but it won't get in until the next release or one after that.

—
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/1738/1188549873@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1738#issuecomment-1188549873", "url": "https://github.com/xrootd/xrootd/issues/1738#issuecomment-1188549873", "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