[37082] in Kerberos
Re: Erratic behavior of full resync process
daemon@ATHENA.MIT.EDU (Tom Yu)
Wed Jun 10 15:55:33 2015
From: Tom Yu <tlyu@mit.edu>
To: Greg Hudson <ghudson@mit.edu>
Date: Wed, 10 Jun 2015 15:55:16 -0400
In-Reply-To: <55788B62.5090602@mit.edu> (Greg Hudson's message of "Wed, 10 Jun
2015 15:09:22 -0400")
Message-ID: <ldvvbeve3tn.fsf@sarnath.mit.edu>
MIME-Version: 1.0
Cc: kerberos@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
Greg Hudson <ghudson@mit.edu> writes:
> /dev/random starvation explains the clock skew errors
This is a troubleshooting point that we should emphasize more:
A Kerberos message might be within the clock skew tolerance when sent,
but for whatever reason, the receiver might delay processing it until it
is no longer within the clock skew tolerance. This can result in clock
skew errors that don't appear to correspond to any observable clock skew
between systems.
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
