Re: Problems with TOD clock data on i386?

["John D. Baker" <jdbaker%mylinuxisp.com@localhost>]

On Mon, 16 Jul 2012, John D. Baker wrote:
> While I'm using ntpd to synchronize the clock (with -g to force large
> initial adjustment), this seems to come too late for PAM/kerberos to
> synchronize with my KDC so my pam-enabled 'sudo' requires a local password
> instead of accepting the realm password for the sudoer trying to
> authenticate.
>
> (This behavior appeared after the KDC changed addresses on my network,
> but all addressing/name-resolution has been verified correct, so that
> leads me to consider time offsets.)

Sorry, I wasn't paying attention.  My Kerberos issues are not related to
timekeeping.  I did more invasive upgrades to the machine that is my kdc
and hosed the credential database.

The issue of this host having trouble reading/deciphering the TOD clock
remains.

--
|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645