[acs] Console log file endianness
Scott Higgins
higgins at jlab.org
Fri Nov 8 10:57:19 EST 2024
Yesterday I was using the console log servers to troubleshoot a boot issue for iocin1.
I noticed that the newest information was added to the top of the list and it made it very
difficult to track what was happening. The boot information was not linear but as the IOC booted
I had to pick back through the log and it was hard to see what was happening in the proper order.
I am definitely for putting the newest information at the end of the file. Then you can go back in time
and figure out what happened in order.
Scott
________________________________
From: acs <acs-bounces at jlab.org> on behalf of Gary Croke via acs <acs at jlab.org>
Sent: Friday, November 8, 2024 10:54 AM
To: acs at jlab.org <acs at jlab.org>
Subject: [acs] Console log file endianness
Folks,
There has been some discussion the past couple of days about the change to console log file ordering. Some have voiced preferring it the old way (newest entries at the end of the file). Does anyone want to chime in with an opinion?
Thanks,
Gary
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/acs/attachments/20241108/518c9f09/attachment.html>
More information about the acs
mailing list