From owner-freebsd-questions@FreeBSD.ORG Sat Oct 18 00:26:11 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D31381065686 for ; Sat, 18 Oct 2008 00:26:11 +0000 (UTC) (envelope-from fbsd06+22=ee1af0ae@mlists.homeunix.com) Received: from fallback-in1.mxes.net (fallback-out1.mxes.net [216.86.168.190]) by mx1.freebsd.org (Postfix) with ESMTP id A658A8FC0C for ; Sat, 18 Oct 2008 00:26:11 +0000 (UTC) (envelope-from fbsd06+22=ee1af0ae@mlists.homeunix.com) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by fallback-in1.mxes.net (Postfix) with ESMTP id 904BA16467C for ; Fri, 17 Oct 2008 20:09:54 -0400 (EDT) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id E2D00D05A5 for ; Fri, 17 Oct 2008 20:09:52 -0400 (EDT) Date: Sat, 18 Oct 2008 01:09:49 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20081018010949.4108e5e7@gumby.homeunix.com.> In-Reply-To: <560f92640810171424v7fd48462qb750cf40229884ac@mail.gmail.com> References: <560f92640810171424v7fd48462qb750cf40229884ac@mail.gmail.com> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: DHCP release/renew lease - elegant solution? 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: Sat, 18 Oct 2008 00:26:11 -0000 On Fri, 17 Oct 2008 14:24:00 -0700 "Nerius Landys" wrote: > The -r flag explicitly releases the current lease, and once > the lease > has been released, the client exits. > > I could put this into a crontab and run it every 12 hours. However, > this does not seem like a very elegant solution to my problem. I am > wondering whether there is a more elegant solution. Before you look for a more elegant solution I suggest you try the inelegant solution and see if it actually works. At the moment all you really know is that rebooting fixes the problem.