From owner-freebsd-questions Thu Aug 24 13:29:32 2000 Delivered-To: freebsd-questions@freebsd.org Received: from diskfarm.firehouse.net (rdu25-12-043.nc.rr.com [24.25.12.43]) by hub.freebsd.org (Postfix) with ESMTP id 42F6037B424 for ; Thu, 24 Aug 2000 13:29:29 -0700 (PDT) Received: (from abc@localhost) by diskfarm.firehouse.net (8.9.3/8.9.3) id UAA03823; Thu, 24 Aug 2000 20:28:01 GMT (envelope-from abc) Date: Thu, 24 Aug 2000 20:28:00 +0000 From: Alan Clegg To: Nathaniel G H Cc: freebsd-questions@freebsd.org Subject: Re: DHCP "refresh" question Message-ID: <20000824202800.A3791@diskfarm.firehouse.net> Mail-Followup-To: Alan Clegg , Nathaniel G H , freebsd-questions@freebsd.org References: <200008231928.MAA03243@mail2.bigmailbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200008231928.MAA03243@mail2.bigmailbox.com>; from bsd_appliance@bemail.org on Wed, Aug 23, 2000 at 12:28:20PM -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Unless the network is lying to me again, Nathaniel G H said: > That is quite obvious, and very simple... but it requires human > intervention. I was trying to find out if there is a way to do > this automatically. It needs to happen when the DHCP address is > no longer valid, but the lease time has not expired. How is a daemon able to determine that the address is no longer valid? It would be quite simple enough to do a: 'killall -HUP dhclient' When you knew the address went sour. AlanC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message