Date: Thu, 19 May 2005 09:10:12 -0700 From: Andrew Sparrow <spadger@spadger.best.vwh.net> To: "Brandon S. Allbery KF8NH" <allbery@ece.cmu.edu> Cc: freebsd-current@freebsd.org Subject: Re: why omshell when no dhcpd ? Message-ID: <20050519091012.A70581@spadger.best.vwh.net> In-Reply-To: <1116516218.2850.0.camel@pyanfar.ece.cmu.edu>; from allbery@ece.cmu.edu on Thu, May 19, 2005 at 11:23:33AM -0400 References: <20815.1116509187@critter.freebsd.dk> <20050519150311.GA9240@crodrigues.org> <1116516218.2850.0.camel@pyanfar.ece.cmu.edu>
index | next in thread | previous in thread | raw e-mail
On Thu, May 19, 2005 at 11:23:33AM -0400, Brandon S. Allbery KF8NH wrote: > It can be used to query a running dhclient for lease information (and > I've wanted to do so a few times only to find that omshell apparently > isn't built on !current...). <AOL> What he said. </AOL> Admittedly you can do most everything without it less elegantly by grovelling around in the lease file and/or killing/re-starting dhclient - but having to build the port (on !current) to get omshell is kind of sub-optimal, especially as omshell is the suggested method of pausing dhclient prior to suspending a mobile client and resuming on a different network. So, killing dhclient works - but it'd be preferable to use rc.suspend/rc.resume to pause/restart dhclient automatically when using a mobile profile. IIRC (been a while), the lack of omshell is reminiscent of building OpenSSL from ports to get some of the standard CA management scripts, even though SSL is in the base system. Cheers, AShome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050519091012.A70581>