This is the mail archive of the
mailing list for the Cygwin project.
Re: 64-bit Heimdal/Cygwin, clock, daylight savings conundrum
- From: ht at inf dot ed dot ac dot uk (Henry S. Thompson)
- To: cygwin at cygwin dot com
- Date: Wed, 09 Apr 2014 10:24:06 +0100
- Subject: Re: 64-bit Heimdal/Cygwin, clock, daylight savings conundrum
- Authentication-results: sourceware.org; auth=none
- References: <f5ba9bu28gl dot fsf at troutbeck dot inf dot ed dot ac dot uk>
[cygcheck attachements got through, but message didn't???]
I'm running 64-bit Cygwin. The problem described here occured both
before and after upgrading from 1.7.28 to 1.7.29. (Cygcheck attached
to previous message).
I'm in the UK, where summer time started 10 days ago.
My Windows 8.1 laptop correctly gained an hour at that time.
Yesterday it gained _another_ hour :-(.
When I corrected the time by hand, kinit to my local host failed:
kinit: krb5_get_init_creds: PREAUTH_FAILED
This usually means timers are out of sync between client (me) and
So I went to work on what I thought was the underlying problem, the
mistaken time. Fixed that, eventually, by fiddling with BIOS clock
and its relation to the system clock.
But the kinit problem didn't go away.
However, _if_ I set the time one hour forward again, kinit succeeds.
True weirdness follows. I have 32-bit install as well (for xemacs)
(Cygcheck attached to previous message). Problem does _not_ manifest
itself there. kinit works _regardless_ of what the windows clock
Has something changed with system clock vs. hardware clock between 32-
and 64-bit cygwin? Or am I looking in the wrong place altogether?
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: firstname.lastname@example.org
[mail from me _always_ has a .sig like this -- mail without it is forged spam]
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple