Print

Print


Well, yes, that was the point and the plan was to make something linke
this. One worry was that moninfo is not specified so it could be anything
including binary information and printing it may cause problems. That's
why it wasn't included in the first place. Given that the DN is specific
to x509 we were leaning to add an option to gsi to simply print it.

Andy


On Thu, 3 Nov 2022, Andrew Melo wrote:

> Hi @bbockelm -- I agree generally with your points -- this is good for now (lets me at least do a grep and sort to find the "heavy hitters"), it would be nice if the logs were one-line w/the regular formatting (e.g timestamps), and we'll certainly need to have a different solution for non-GSI (e.g. token) authentication
>
> --
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1738#issuecomment-1302283042
> You are receiving this because you were mentioned.
>
> Message ID: ***@***.***>


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/1302413071@github.com>

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