DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:subject:references:from:date:in-reply-to
	:message-id:mime-version:content-type; q=dns; s=default; b=vnVZR
	CM7JyquzbWaORFFkumINMcvKPhoc+FpG3jOyVhwp8OUDCORczWTcGHNBlRioUU1G
	BNqj5hFKyW/DVtHyW9pTUNla8dPZFxPooTcHrVMHuz2+G5gWbHF7PHk2OxUqdqqw
	lL1H+iiZU9p3viUyXHpTEzMKx39vzSDszw/rL0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
Subject: Re: 64-bit Heimdal/Cygwin, clock, daylight savings conundrum
References: <f5ba9bu28gl.fsf@troutbeck.inf.ed.ac.uk>
From: ht@inf.ed.ac.uk (Henry S. Thompson)
Date: Wed, 09 Apr 2014 10:24:06 +0100
In-Reply-To: <f5ba9bu28gl.fsf@troutbeck.inf.ed.ac.uk> (Henry S. Thompson's message of "Wed\, 09 Apr 2014 09\:49\:46 +0100")
Message-ID: <f5b61mi26vd.fsf@troutbeck.inf.ed.ac.uk>
User-Agent: Gnus/5.101 (Gnus v5.10.10) XEmacs/21.5-b33 (linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

[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
 [pwd]
 kinit: krb5_get_init_creds: PREAUTH_FAILED

This usually means timers are out of sync between client (me) and
server.

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
says.

Has something changed with system clock vs. hardware clock between 32-
and 64-bit cygwin?  Or am I looking in the wrong place altogether?

ht
-- 
       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: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

--
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