Date: Thu, 29 Mar 2007 23:58:57 +0400 From: Andrey Chernov <ache@freebsd.org> To: John Baldwin <jhb@freebsd.org> Cc: cvs-src@freebsd.org, Mike Makonnen <mtm@freebsd.org>, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/etc network.subr Message-ID: <20070329195857.GA11737@nagual.pp.ru> In-Reply-To: <200703291534.46417.jhb@freebsd.org> References: <200703291055.l2TAtYu4038445@repoman.freebsd.org> <20070329172409.GA38703@rogue.navcom.lan> <20070329190812.GA11138@nagual.pp.ru> <200703291534.46417.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 29, 2007 at 03:34:45PM -0400, John Baldwin wrote:
> The change in v1.28 fixed a similar warning where you'd get something like
>
> /etc/rc.d/dhclient: WARNING: $background_dhclient_bge0 is not set properly
>
> (where bge0 is an interface name). 1.28 fixed the warning for me, but I don't
> use background_dhclient and have none of the variables set. Maybe Andrey is
> seeing a warning in the non-default case when a variable is set?
I have plain DHCP and don't use background_dhclient too. I wonder why
somebody have not see it. Look at this lines from v1.28:
background_dhclient=`get_if_var $ifn background_dhclient_IF $background_dhclient`
if checkyesno background_dhclient; then
Since background_dhclient_fxp0="" automatically set earlier,
background_dhclient evaluates to "" too.
Then checkyesno background_dhclient produces this warning.
--
http://ache.pp.ru/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070329195857.GA11737>