From owner-freebsd-stable  Tue Mar 28 14: 5:57 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from smtp1.medianstrip.net (host30.thirteen.net [206.113.38.30])
	by hub.freebsd.org (Postfix) with ESMTP id A7D3637BE60
	for <stable@freebsd.org>; Tue, 28 Mar 2000 14:05:54 -0800 (PST)
	(envelope-from mike@medianstrip.net)
Received: by smtp1.medianstrip.net (Postfix, from userid 1000)
	id 59DCB59A4; Tue, 28 Mar 2000 17:05:41 -0500 (EST)
Date: Tue, 28 Mar 2000 17:05:41 -0500
From: mike ryan <mikeryan@post.harvard.edu>
To: stable@freebsd.org
Subject: dhclient failure due to timeout limit on select
Message-ID: <20000328170541.A25874@medianstrip.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

observed on 4-stable, though this appears to be equally relevant on
3-stable and current:

select() returns EINVAL on timeouts of more than 100 million seconds
due to an apparently arbitrary limit in itimerfix().  this causes
dhclient to bail after obtaining a lease exceeding that limit.  my
rcn cable modem service, for example, sets a renewal time of
1073741823 seconds.  while this pretty much means "don't bother
renewing", it'd still be nice if dhclient didn't give up.

is there a reason why there needs to be a 100000000 second limit in
select and/or itimerfix?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message