➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ngie
Recipients belopolsky, ngie, r.david.murray, terry.reedy
Date 2012-09-13.22:11:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1347574279.86.0.277163139356.issue15942@psf.upfronthosting.co.za>
In-reply-to
Content 
Ok. Turns out I got this backwards. The BIOS clock is set to UTC (which works with the CentOS install on the same drive) and Windows assumes the clock is set to local time [1]. I'll follow it up with the my $work lab team, but it would be nice if this could be tuned properly to report the proper time according to Windows (even if the bloody clock/tz was wrong to begin with).

1. https://help.ubuntu.com/community/UbuntuTime
History
Date User Action Args
2012-09-13 22:11:20ngiesetrecipients: + ngie, terry.reedy, belopolsky, r.david.murray
2012-09-13 22:11:19ngiesetmessageid: <1347574279.86.0.277163139356.issue15942@psf.upfronthosting.co.za>
2012-09-13 22:11:19ngielinkissue15942 messages
2012-09-13 22:11:18ngiecreate