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: EPICS_TIMEZONE and TZ on RTEMS |
From: | Matt Rippa <[email protected]> |
To: | "J. Lewis Muir" <[email protected]> |
Cc: | Talk EPICS Tech <[email protected]> |
Date: | Mon, 25 Apr 2016 12:42:11 -1000 |
On 4/25/16 4:12 PM, Matt Rippa wrote:
> Hello,
>
> On EPICS 3.14.12.4 and RTEMS 4.10.2 I can't seem to control the
> timezone at runtime.
> My BSP is the mvme2700.
>
>
> EPICS base is build with
> base/configure/CONFIG_SITE_ENV:EPICS_TIMEZONE=CUS::360:031302:110602
>
> An oversight, but I was thinking it didn't matter and I could just
> change things in my startup script. I tried to re-define this in my
> startup script before iocInit() as follows:
>
> #Hawaii is standard time and never moves their clocks
> epicsEnvSet("EPICS_TIMEZONE", "HST::600:0:0")
Hello, Matt.
I don't think that's a valid value: the last two parts are supposed to
be "mmddhh", but you've just got a single digit ('0') for each.
> Then I found the link below so I tried
>
> epicsEnvSet("TZ", "HST10")
>
> In both cases, my timezone persisted with Central US time, UTC-5
> hours.
On VxWorks, I set the "TIMEZONE" environment variable instead of
"EPICS_TIMEZONE". I suspect there's a reason for that, but I don't
remember what it is, and I don't know if the same applies to RTEMS.
> My latest AppDevGuide (Oct. 5th, 2015) does not describe it. Is this
> documented anywhere else?
The documentation I've been using is the comment for EPICS_TIMEZONE in
configure/CONFIG_SITE_ENV.
Regards,
Lewis