From: Denis Excoffier <Denis.Excoffier@free.fr>
To: cygwin@cygwin.com
Subject: Re: cygcheck's understanding of TZ
Date: Fri, 10 Jun 2011 17:44:00 -0000 [thread overview]
Message-ID: <1D852702-CB83-4DAA-A31A-D3F8A01E432A@free.fr> (raw)
In-Reply-To: <20110610142124.GA5849@ednor.casa.cgf.cx>
On 2011-06-10 16:21, Christopher Faylor wrote:
> 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.
Wrong by 1h is not pinpoint accuracy (i think). Here is a patch that
describes what i mean:
--- ./cygwin-snapshot-20110608-1/winsup/utils/cygcheck.cc
2011-04-07 08:09:28.000000000 +0200
+++ ./cygwin-snapshot-20110608-1.new/winsup/utils/cygcheck.cc
2011-06-10 19:31:59.000000000 +0200
@@ -1398,7 +1398,9 @@
printf ("\nCygwin Configuration Diagnostics\n");
time (&now);
- printf ("Current System Time: %s\n", ctime (&now));
+ /* UTC is better than local time for reference purposes, and also
does
+ not depend on TZ, which is problematic in certain cases under
msvcrt.dll */
+ printf ("Current System Time (UTC): %s\n", asctime (gmtime (&now)));
OSVERSIONINFOEX osversion;
osversion.dwOSVersionInfoSize = sizeof (OSVERSIONINFOEX);
Also to be considered similar patches for the other programs that
don't link
with cygwin1.dll, if necessary.
Hope this helps.
Regards.
Denis Excoffier.
--
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-10 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]
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 [this message]
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=1D852702-CB83-4DAA-A31A-D3F8A01E432A@free.fr \
--to=denis.excoffier@free.fr \
--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).