Re: r239356: does it mean,

Hello, Ian.
You wrote 22 =C1=D7=C7=D5=D3=D4=C1 2012 =C7., 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 -CURR=
ENT
 with adding of ``synchronous_dhclient=3D"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).

 And rc.conf(5) explains `devd_enable' as:

 Run devd(8) to handle device added, removed or unknown events from the ker=
nel.

 And doesn't say a word about network link state.

--=20
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>

_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"