| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 <2007> 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 <2007> 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | RE: Daylight savings time |
| From: | "Thompson, David H." <[email protected]> |
| To: | "Gurd, Pamela A." <[email protected]>, [email protected] |
| Date: | Tue, 13 Mar 2007 09:30:56 -0400 |
|
Looks like a no-win situation all
around.
From: Gurd, Pamela A. Sent: Tuesday, March 13, 2007 9:07 AM To: Thompson, David H.; [email protected] Subject: RE: Daylight savings time Moving TIMEZONE to the post-startup created a different problem, however – now the BootTime value is an hour too early.
-----Original
Message-----
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?
|