Date: Fri, 25 Jan 2008 16:16:14 -0500 From: Yousif Hassan <yousif@alumni.jmu.edu> To: Kevin Downey <redchin@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: network interface monitoring? Message-ID: <1201295774.1536.1.camel@localhost> In-Reply-To: <1d3ed48c0801251228t3f9e69a0x54bae7b261f2cbf3@mail.gmail.com> References: <1201125022.2106.67.camel@localhost> <20080123222047.GA14264@lor.one-eyed-alien.net> <1201190313.2591.7.camel@localhost> <20080124163634.GA25331@lor.one-eyed-alien.net> <1201198042.19736.5.camel@localhost> <20080125051059.GA22410@cdnetworks.co.kr> <1201275694.1537.13.camel@localhost> <1d3ed48c0801251228t3f9e69a0x54bae7b261f2cbf3@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> the rc.conf manpage has a few options regarding the function of dhcp including: > > synchronous_dhclient > (is currently in beta test. Set to ``bool'') to start > dhclient(8) only in response to interface events and not syn- > chronously at startup. This behavior can be overridden on a > per-interface basis by replacing the ``DHCP'' keyword in the > ifconfig_<interface> variable with ``SYNCDHCP'' or > ``NOSYNCDHCP''. > > and > > background_dhclient > (bool) Set to ``YES'' to start the DHCP client in background. > This can cause trouble with applications depending on a work- > ing network, but it will provide a faster startup in many > cases. What a great list. Very useful suggestions, thanks! The behavior you get from setting synchronous_dhclient="NO" is exactly what I was looking for.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1201295774.1536.1.camel>