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