cygcheck's understanding of TZ
Fri Jun 10 17:44:00 GMT 2011
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
> 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:
2011-04-07 08:09:28.000000000 +0200
2011-06-10 19:31:59.000000000 +0200
@@ -1398,7 +1398,9 @@
printf ("\nCygwin Configuration Diagnostics\n");
- printf ("Current System Time: %s\n", ctime (&now));
+ /* UTC is better than local time for reference purposes, and also
+ not depend on TZ, which is problematic in certain cases under
+ printf ("Current System Time (UTC): %s\n", asctime (gmtime (&now)));
osversion.dwOSVersionInfoSize = sizeof (OSVERSIONINFOEX);
Also to be considered similar patches for the other programs that
with cygwin1.dll, if necessary.
Hope this helps.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin