r239356: does it mean, that synchronous dhcp and dhcplcinet with
disabled devd gone?
Slawa Olhovchenkov
slw at zxy.spb.ru
Tue Aug 21 22:58:14 UTC 2012
On Wed, Aug 22, 2012 at 02:36:23AM +0400, Lev Serebryakov wrote:
> Hello, Ian.
> You wrote 22 августа 2012 г., 1:38:04:
>
> IL> For example, this script can replace devd as a daemon that restarts
> IL> dhclient when any link comes back up...
>
> IL> Of course the right thing to do is invoke the proper rc scripts rather
> IL> than dhclient directly... this is just to illustrate how easy it is to
> IL> replace devd if your needs are specialized.
> [sigh]
> Everything worked with 8.x without problems. It worked with 9.x and -CURRENT
> with adding of ``synchronous_dhclient="YES"'' into /etc/rc.conf (And
> it cost me about 2 hours of investigation, why dhclient stops to
> start after upgrade). Next I'll need to write some script. Is it Ok
> to you?
>
> Yes, I understand problem with laptops, which change wire and
> wireless networks and need to re-acquire new address. But it should
> be soleved other way. And jhb@ already posted proper solution, BTW!
>
> And, as side note, ``man rc.cof'' says NOTHING about relation of devd
> and ``synchronous_dhclient'' setting! It says about ``start
> dhclient(8) synchronously at startup'' without explaining, that
> without this option and with devd disabled, dhclient WILL NOT START
> AT ALL! And relations between devd and dhclient are not documented at
> all in: rc.conf(5), dhclient(8), devd.conf(5) and devd(8).
Time ago synchronous_dhclient is waiting for obtain IP by dhcpclient.
w/o synchronous_dhclient and ifconfig_bge0="DHCP" dhcpclient run in
background and don't paused boot while obtaining IP address.
On perinterface basis: ifconfig_bge0="SYNCDHCP" or ifconfig_bge0="NOSYNCDHCP"
Background start of dhcpclient currently by devd, on UP event on
ethernet interface. This introduction in 6.2. 2006-08-22.
More information about the freebsd-current
mailing list