Something very weird just happened here and we are still
trying to figure out why.
Running iocs were updated by just setting the TIMEZONE environment
variable and all is fine.
Iocs that were rebooted today had the TIMEZONE variable set
in a common startup script that is called before everything else. Those
IOCS seemed to display the correct time but camonitor was reporting the time an
hour earlier. The hardware timing module displayed the time an hour later
than it was. The timing system was not rebooted and had the correct time on the
hardware link.
We fixed the problem by moving the TIMEZONE setting to the
post-startup script.
Has anyone else had similar problems?