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:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=UIVjnYNJE/A1tNBAqbFrw7aeCxYXm+0OZ/FrLIpWC6tbg4qiDPaWj
	OpPoI7xqvyJj+3rgriBYw8OlDmtAk5H2XA+pNWd9Ml+wMJylJAAI8jAbWhyV/QlP
	mXpG6jdVtEw0HKTke75ASvikJp4gSc35jr9s7/PM0LsXNzeTL2x1MI=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Wed, 9 Apr 2014 12:10:04 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 64-bit Heimdal/Cygwin, clock, daylight savings conundrum
Message-ID: <20140409101004.GO2437@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <f5ba9bu28gl DOT fsf AT troutbeck DOT inf DOT ed DOT ac DOT uk> <f5b61mi26vd DOT fsf AT troutbeck DOT inf DOT ed DOT ac DOT uk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="AzNpbZlgThVzWita"
Content-Disposition: inline
In-Reply-To: <f5b61mi26vd.fsf@troutbeck.inf.ed.ac.uk>
User-Agent: Mutt/1.5.21 (2010-09-15)

--AzNpbZlgThVzWita
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Apr  9 10:24, Henry S. Thompson wrote:
> [cygcheck attachements got through, but message didn't???]
>=20
> 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).
>=20
> I'm in the UK, where summer time started 10 days ago.
>=20
> My Windows 8.1 laptop correctly gained an hour at that time.
>=20
> Yesterday it gained _another_ hour :-(.
>=20
> When I corrected the time by hand, kinit to my local host failed:
>=20
>  > kinit
>  [pwd]
>  kinit: krb5_get_init_creds: PREAUTH_FAILED
>=20
> This usually means timers are out of sync between client (me) and
> server.
>=20
> 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.
>=20
> But the kinit problem didn't go away.
>=20
> However, _if_ I set the time one hour forward again, kinit succeeds.
>=20
> 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.
>=20
> Has something changed with system clock vs. hardware clock between 32-
> and 64-bit cygwin?  Or am I looking in the wrong place altogether?

Hmm, maybe.  Apart from time_t being 64 bit (32 bit on i686), the
code for time handling is identical.  What's your $TZ set to?


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--AzNpbZlgThVzWita
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTRRx8AAoJEPU2Bp2uRE+gmKEP/iIhIswKwV9t7KuwfROoI8cX
vM+b8LIg1fMH3dnlaBcJO5gi67SjV/hvAdbIMagDN/cJubulfrswrjfDiaBabvQQ
e4Jha2aAL1OTQmD5Z+Ti/xy1gQRdFWUfaLYeRq0Zg6140AQVrGZ7BZRu0vapEbfj
Eea1RSBtve1o0DqZ1cTsEfYsHgD3jld1IpEWfcPgXLuikC7rJuvTpEReyx/EFtg4
rTyet2lgdsHrc7ufkAh4Dh6fsS/kmiXGNj881I2LhUDC+5DXquRa1oPDkqW52Zdu
EMphX+HkqaUOROB0QHuCeiXjgaoK3zidXg3u3wxtbm/vNrnlXzOvOjh8zeUs7P5Q
l0csd3vsyYEy4jFUfImSCBhtEWlFL03LBwxOdoyYSqs2vvMO+DbosJT2NnC5dBib
twN//cU4yzGKz61c0ob5zgELzQM4u6bN/lR9NCB+Cqwm8VKpBQKW8KXyqAszU4w+
t2rLXhOeh9VAb6klsIwZisOfXLKprNG8af2ZLwejYGWion4+k3kNj+Iq0w3wx94t
f7m03IvXnXjRzyIyICoWU/V3PGYYjHTcMpgkqMqu4T4o6BtTlydX2svYqryLMlqr
8UPqG40ms3H0k5MligItObfUoATxJReK9cG3iltElsNuLIXn2N5x47J1ZKjAJLL2
gyh+p85+DcCMHFSjlBIo
=6j45
-----END PGP SIGNATURE-----

--AzNpbZlgThVzWita--