XRootD client log messages have a timestamp with microsecond precision. However, the SSI log messages only have second precision. Example:

|201210 12:47:51 12355 T 0#0 Ssi_TaskKill: Status=isDone defer=True mhPend=False |
|201210 12:47:51 12355 T 0#0 Ssi_TaskReqFin: Task removal deferred. 201210 12:47:51 12355 T 0#0 Ssi_TaskXeqEnd: Calling TaskFinished; mhPend=False defer=True |
|201210 12:47:51 12355 S 0# Ssi_RelTask: Deleting task=0x1b66200 id=0 201210 12:47:51 12355 S 0# Ssi_Unprovision: Closing /ctafrontend |

Andy said:

those messages can get high precision, I just didn't expose a mechanism to turn that on. You get a choice, a settable call that you can use during initialization or an envar, when set, turns on high precision.

Either of these options would be fine, the environment variable is probably slightly preferable as it doesn't require changing any code.

Thanks!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

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