Print

Print

It certainly would. Now, would you consider creating a pull request that fixes the problem? That way you get complete credit for not only identifying the problem but fixing it as well :-)

Looks simple, but have not done this, since the data to be printed (from deep inside the Kerberos service ticket) will be cleaned up before we hit that particular Fatal() log line - so would need to have two 'Fatal()' (then do the cleanup in two places), or copy to some temporary string (and clean that up). There probably is some project-wide "how to do this best"-approach here..

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: <xrootd/xrootd/issues/1948/1470098919@github.com>

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