X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,TW_YG,UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org X-Yahoo-SMTP: jenXL62swBAWhMTL3wnej93oaS0ClBQOAKs8jbEbx_o- Date: Fri, 10 Jun 2011 10:21:24 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygcheck's understanding of TZ Message-ID: <20110610142124.GA5849@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20110609094631 DOT 56364lzi64m7t4d3 AT messagerie DOT si DOT c-s DOT fr> <4DF10C13 DOT 3040208 AT cwilson DOT fastmail DOT fm> <811AA35F-E300-46E5-9FE3-EE7D5E58194B AT free DOT fr> <20110609210632 DOT GA1457 AT ednor DOT casa DOT cgf DOT cx> <4E1EF031-A2E0-4238-BD23-5089E2D7670F AT free DOT fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E1EF031-A2E0-4238-BD23-5089E2D7670F@free.fr> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Fri, Jun 10, 2011 at 09:24:45AM +0200, Denis Excoffier wrote: > >On 2011-06-09 23:06, Christopher Faylor wrote: > >> We're not changing anything. Having the date there is useful. > >I (OP) need to use TZ=Europe/Monaco (or similar, or >with an absolute name) to make my applications work, >including date(1). > >Currently the `Current System Time' line is: >- incorrect at least in my (legitimate) use of TZ, >- not fully adequate for reference purposes since > it does not specify the time zone. > >It therefore deserves improvement. > >But since it seems difficult to make it correct due to specific >constraints (windows program), feel free not to modify it. Users like >me will have to 'export TZ=UTC' before 'cygcheck -s'. Not difficult. When I said the date was useful I was obviously referring to it being useful in the context for which "cygcheck -s" is used - reporting configuration info to the cygwin mailing list. That's why "cygcheck -s" exists. In that context, knowing, generally, when the command was run on the reporter's system is useful. >Or change cygcheck's specification for the better: use >UTC date instead, since printing UTC date does not >depend/rely on TZ: >Current System Time (UTC): Thu Jun 09 07:07:14 2011 > >>Again: you shouldn't use "cygcheck -s" as a method to find the system >>date. > >Sorry, next time i'll use 'alias foobar' instead of 'alias cygdate'. Actually an alias does nothing to illustrate this issue. Just cutting and pasting the output from cygcheck -s would have been enough to show what you're talking about. Unless you are reporting a problem with aliases, providing an alias implies that you actually intend to use the alias for some purpose. But, in any event, we still have no idea (since you haven't provided details) why you find it so crucial for cygcheck to report the date with pinpoint accuracy but if this is required for your purposes then you should "feel free" to provide a patch to cygcheck.cc. If you don't want to provide a patch then you could also investigate modifying the cygcheck output via sed to match what you require. cgf -- 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