From 241ec6e5c75b6872a32c5e05c17ebb4238e120e0 Mon Sep 17 00:00:00 2001 From: David Benjamin Date: Mon, 19 Aug 2013 05:49:56 -0400 Subject: Bump find_or_insert_uid's time limit Basing it on krb4's CLOCK_SKEW value doesn't make any sense. We pick 900 because it is just over 128 + 256 + 512, the longest group of three timeouts in the retransmit schedule used by the zephyrd. This allows us to miss two packets in a row and still be fine. --- lib/Zinternal.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'lib') diff --git a/lib/Zinternal.c b/lib/Zinternal.c index ace1a81..07cd342 100644 --- a/lib/Zinternal.c +++ b/lib/Zinternal.c @@ -145,9 +145,9 @@ find_or_insert_uid(ZUnique_Id_t *uid, return 0; } - /* Age the uid buffer, discarding any uids older than the clock skew. */ + /* Age the uid buffer, discarding any uids older than the time limit. */ time(&now); - while (num && (now - buffer[start % size].t) > CLOCK_SKEW) + while (num && (now - buffer[start % size].t) > Z_FILTERTIMELIMIT) start++, num--; start %= size; -- cgit v1.2.3