EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: a short reference of the time zone abbreviation in CONFIG_SITE_ENV
From: Andrew Johnson <[email protected]>
To: <[email protected]>
Date: Fri, 22 Sep 2017 11:16:37 -0500
Hi Han,

On 09/22/2017 03:00 AM, Jeong Han Lee wrote:
> # Time service:
> # EPICS_TIMEZONE
> #    Local timezone info for vxWorks and RTEMS.  The format is
> #        <name>::<minutesWest>:<start daylight>:<end daylight>
> #    where the start and end are mmddhh - that is month,day,hour
> #    e.g. for ANL in 2018: EPICS_TIMEZONE=CUS::360:031102:110402
> #    The future dates below assume the rules don't get changed;
> #    see http://www.timeanddate.com/time/dst/2018.html to check.
> #
> ---- snip snip -----
> 
>    I think, it uses the time zone abbreviation as <name>. And I could
> find them quite easily and quickly, However, if we can have the link in
> that file (CONFIG_SITE_ENV) in the same way of DST, for example,
> 
> ```
> <name> is the Time Zone Abbreviation;
> see https://en.wikipedia.org/wiki/List_of_time_zone_abbreviations
> ```
> it may give users an easy way to access them.

The <name> part of that string is arbitrary; the OS only uses it in the
output generated when converting a timestamp to a string with a %Z
format string, so it doesn't really matter what you put in there as long
as you understand that name locally (assuming you even use %Z in your
conversion formats). With that in mind I don't think we need to provide
a link to a standard list of time-zone names, but I will document the
fact that <name> is used only for %Z. Here's my new wording:

> # Time service:
> # EPICS_TIMEZONE
> #	Local timezone info for vxWorks and RTEMS.  The format is
> #	    <name>::<minutesWest>:<startDST>:<endDST>
> #	where <name> is only used by strftime() for %Z conversions,
> #	and <startDST> and <endDST> are mmddhh - that is month,day,hour
> #	e.g. for ANL in 2018: EPICS_TIMEZONE=CUS::360:031102:110402
> #	The future dates below assume the rules don't get changed;
> #	see http://www.timeanddate.com/time/dst/2018.html to check.

Is that a sufficient solution?

- Andrew

-- 
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon

Replies:
Re: a short reference of the time zone abbreviation in CONFIG_SITE_ENV Jeong Han Lee
References:
a short reference of the time zone abbreviation in CONFIG_SITE_ENV Jeong Han Lee

Navigate by Date:
Prev: a short reference of the time zone abbreviation in CONFIG_SITE_ENV Jeong Han Lee
Next: Re: a short reference of the time zone abbreviation in CONFIG_SITE_ENV Jeong Han Lee
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: a short reference of the time zone abbreviation in CONFIG_SITE_ENV Jeong Han Lee
Next: Re: a short reference of the time zone abbreviation in CONFIG_SITE_ENV Jeong Han Lee
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
ANJ, 21 Dec 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·