Experimental Physics and Industrial Control System
|
Steve Lewis wrote:
Does anyone have a convenient way to construct the value for the VxWorks
TIMEZONE environment variable? It looks something like this
"TIMEZONE=PDT::480:040305:103005"
Note that this value for the vxWorks TIMEZONE variable is wrong - the
last two digits in each triplet tell vxWorks the _hour_ of the change,
not the year, thus they should almost always be 02 since most states
change to/from summer time at 2am.
The format is described in the configure/CONFIG_SITE_ENV file of most
recent R3.14 releases.
- Andrew
--
English probably arose from Normans trying to pick up Saxon girls.
- References:
- VxWorks TIMEZONE hack, anyone? Steve Lewis
- Navigate by Date:
- Prev:
RE: VxWorks TIMEZONE hack, anyone? Rees, NP (Nick)
- Next:
Channel access problem on cygwin IOC Mark Rivers
- 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
- Navigate by Thread:
- Prev:
Re: VxWorks TIMEZONE hack, anyone? Steven Hartman
- Next:
RE: VxWorks TIMEZONE hack, anyone? Rees, NP (Nick)
- 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
|
ANJ, 02 Sep 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|