From owner-freebsd-questions@FreeBSD.ORG Tue May 2 15:50:22 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1F5516A402 for ; Tue, 2 May 2006 15:50:22 +0000 (UTC) (envelope-from atom.powers@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45A8F43D4C for ; Tue, 2 May 2006 15:50:20 +0000 (GMT) (envelope-from atom.powers@gmail.com) Received: by nz-out-0102.google.com with SMTP id 12so1580801nzp for ; Tue, 02 May 2006 08:50:17 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MDYBDJaBMMpyUFER65kjQBaNdplmlwoeX/Zpo2VAlSVclCjUG9DhwSfghQTkLy0tMPQ/9kXI9qmW5Ex/m8ONbcnvweiAVKB4Rzt0Y7XHbk5+XO2PqRWveC2zvmHkFB9RMbxxc2vQ1jEYa3Pr3ZsLJ4AU7maQpeCEJ/Z0Jie6tf0= Received: by 10.65.203.10 with SMTP id f10mr497227qbq; Tue, 02 May 2006 08:50:17 -0700 (PDT) Received: by 10.65.150.9 with HTTP; Tue, 2 May 2006 08:50:17 -0700 (PDT) Message-ID: Date: Tue, 2 May 2006 08:50:17 -0700 From: "Atom Powers" To: freebsd-questions@freebsd.org In-Reply-To: <44hd48v87r.fsf@be-well.ilk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <44hd48v87r.fsf@be-well.ilk.org> Cc: fbsd@a1poweruser.com Subject: Re: force lease renewal from dhcpd X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 15:50:22 -0000 On 02 May 2006 09:59:04 -0400, Lowell Gilbert wrote: > "fbsd" writes: > > > Is there some way to force all leases under dhcpd to perform lease > > renewal routine? > > Even if the dhcpd implements INFORM, most clients won't. > > In practice, if you want the clients to update before their existing > lease is due for renewal, you generally have to go around to the > clients individually. Or plan ahead. If you know you will be changing some lease options you should set the lease time down to something small at least $(current_lease_period) seconds ahead of time. Then you can be fairly certain that all systems will get a new lease within $(new_lease_period) seconds of you change. Afterwards you can increase the lease period back up. Of course, this assumes you were not handing out "infinite" lease periods. -- -- Perfection is just a word I use occasionally with mustard. --Atom Powers--