On Apr 9 10:24, Henry S. Thompson wrote: > [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?
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 -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
pgp_cFDaATRHX.pgp
Description: PGP signature
