X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=0.5 required=5.0	tests=AWL,BAYES_50,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,TW_YG,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <20110609094631.56364lzi64m7t4d3@messagerie.si.c-s.fr>
References: <20110609094631 DOT 56364lzi64m7t4d3 AT messagerie DOT si DOT c-s DOT fr>
From: Edward McGuire <cygwin DOT com AT metaed DOT com>
Date: Thu, 9 Jun 2011 12:39:04 -0500
Message-ID: <BANLkTinwkd50q5JdugNRO8wfQrJ00syD+w@mail.gmail.com>
Subject: Re: cygcheck's understanding of TZ
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id p59HdhYS000556

On Thu, Jun 9, 2011 at 02:46, EXCOFFIER Denis
<denis DOT excoffier AT c-s DOT fr> wrote:
> 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
> [snip]
> jupiter% (setenv TZ /usr/share/zoneinfo/Europe/Monaco; date; cygdate)

There are two standard syntaxes for TZ. One begins with a timezone
name, the other begins with a colon (:). If you supply a colon, then
the rest of the string is interpreted in an operating system
specific manner. GNU interprets it as a pathname. And Cygwin uses
GNU's time library.

Naïvely, I thought you might just lack a colon on the front of the
pathname. I confirmed time(1) honors the pathname syntax. But
cygcheck(1) mysteriously interprets all pathnames as GMT + 1 hour:

$ TZ=:/usr/share/zoneinfo/US/Central cygcheck -s | head -3 | tail -1
Current System Time: Thu Jun 09 18:23:42 2011
$ TZ=:/usr/share/zoneinfo/Europe/Monaco cygcheck -s | head -3 | tail -1
Current System Time: Thu Jun 09 18:23:49 2011
$ TZ=:/usr/share/zoneinfo/GMT cygcheck -s | head -3 | tail -1
Current System Time: Thu Jun 09 18:23:56 2011
$ TZ=:/usr/share/zoneinfo/Asia/Calcutta cygcheck -s | head -3 | tail -1
Current System Time: Thu Jun 09 18:23:59 2011

It gets local time right:

$ cygcheck -s | head -3 | tail -1
Current System Time: Thu Jun 09 12:25:04 2011

And it gets GMT right:

$ TZ=GMT cygcheck -s | head -3 | tail -1
Current System Time: Thu Jun 09 17:31:32 2011

So cygcheck(1) is honoring TZ, but it trips over a pathname in a
way that date(1) does not.

Cheers,

MetaEd

--
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