From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: cygcheck's understanding of TZ
Date: Thu, 09 Jun 2011 17:44:00 -0000 [thread overview]
Message-ID: <0105D5C1E0353146B1B222348B0411A209ED1BF8F2@NIHMLBX02.nih.gov> (raw)
In-Reply-To: <4DF07C22.7050205@towo.net>
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: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-06-09 17:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 7:47 EXCOFFIER Denis
2011-06-09 7:54 ` Thomas Wolff
2011-06-09 17:44 ` Buchbinder, Barry (NIH/NIAID) [E] [this message]
2011-06-09 17:39 ` Edward McGuire
2011-06-09 18:08 ` Charles Wilson
2011-06-09 19:27 ` Edward McGuire
2011-06-09 19:50 ` Denis Excoffier
2011-06-09 21:06 ` Christopher Faylor
2011-06-09 22:01 ` Edward McGuire
2011-06-10 7:25 ` Denis Excoffier
2011-06-10 14:07 ` Edward McGuire
2011-06-10 14:30 ` Christopher Faylor
2011-06-10 17:44 ` Denis Excoffier
2011-06-13 15:07 ` Edward McGuire
2011-06-13 15:34 ` Christopher Faylor
2011-06-14 15:05 ` Lee Maschmeyer
2011-06-14 15:28 ` Christopher Faylor
2011-06-14 17:30 ` Lee Maschmeyer
2011-06-14 17:51 ` Edward McGuire
2011-06-14 18:35 ` Lee Maschmeyer
2011-06-14 19:19 ` Edward McGuire
2011-06-14 19:22 ` Christopher Faylor
2011-06-14 19:21 ` Christopher Faylor
2011-06-09 18:58 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0105D5C1E0353146B1B222348B0411A209ED1BF8F2@NIHMLBX02.nih.gov \
--to=bbuchbinder@niaid.nih.gov \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).