DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=PnyWnxEj1U85Ok2o
	PcWLG9m5rQ4E+PhH8SpzKwRceHygSNScu4r2lholNG2LqKvHBpZ9LUeb2N9EN2rv
	jVx79afGuqNPe4ffpMb1yE0rKmabiyxXblg8H7DbkHMUQI3uX9knkuimvyO9WtPT
	6zIFMhHJ/LnNkl1nibkCYgsH7pE=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Wed, 9 Apr 2014 17:22:30 +0400
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <1142907573.20140409172230@yandex.ru>
To: ht@inf.ed.ac.uk (Henry S. Thompson), cygwin@cygwin.com
Subject: Re: 64-bit Heimdal/Cygwin, clock, daylight savings conundrum
In-Reply-To: <f5b61mi26vd.fsf@troutbeck.inf.ed.ac.uk>
References: <f5ba9bu28gl.fsf@troutbeck.inf.ed.ac.uk> <f5b61mi26vd.fsf@troutbeck.inf.ed.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Henry S. Thompson!

> 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 :-(.

This is suspicious. I hope, there was no changes to DST dates in UK recently?
How does it appear to you?
I.e. if your time zone in Windows set correctly, what time the system clock
show, and how it is converted to UTC?
Do you have real time synchronization set up?

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

Could it be a server issue at this point? Is it in the same timezone, as
yourself?

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


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 09.04.2014, <17:18>

Sorry for my terrible english...


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