This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: cygcheck's understanding of TZ

Thomas Wolff sent the following at Thursday, June 09, 2011 3:54 AM
>Am 09.06.2011 09:46, schrieb EXCOFFIER Denis:
>>> It seems that /usr/bin/cygcheck does not interpret TZ the same way as
>> /usr/bin/date does, in the case TZ is set to a file name, like in the
>> following example:
>> (under tcsh)
>> jupiter% alias cygdate 'cygcheck -s | head -3'
>> jupiter% (setenv TZ /usr/share/zoneinfo/Europe/Monaco; date; cygdate)
>> Thu Jun  9 09:07:13 CEST 2011
>Set TZ to the name of a timezone, not a file name, e.g. (using bash)
>TZ=CET date.

u>Am 09.06.2011 09:46, schrieb EXCOFFIER Denis:

I'm confused.

Using /usr/sbin/tzselect to find TZ ends with the following (questions
have been deleted):

| You can make this change permanent for yourself by appending the line
|         TZ='Europe/Monaco'; export TZ
| to the file '.profile' in your home directory; then log out and log in again.
| Here is that TZ value again, this time on standard output so that you
| can use the /usr/sbin/tzselect command in shell scripts:
| Europe/Monaco

So my question is whether one would really use CEST or the result of
tzseelct.  (Note:  I kept the OP's example of Monaco - I am really
in the U.S.)  And if it is something like CEST, what does one do in
the U.S., where some do not go on Daylight Savings (Summer) Time?

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]