On Thu, Apr 09, 2009 at 05:12:53PM +0400, Dmitry Marakasov wrote: > * Dag-Erling Smorgrav (d...@freebsd.org) wrote: > > > Modified: head/etc/defaults/rc.conf > > ============================================================================== > > --- head/etc/defaults/rc.conf Thu Mar 19 12:39:13 2009 > > (r190030) > > +++ head/etc/defaults/rc.conf Thu Mar 19 12:48:00 2009 > > (r190031) > > @@ -101,7 +101,7 @@ nisdomainname="NO" # Set to NIS domain > > dhclient_program="/sbin/dhclient" # Path to dhcp client program. > > dhclient_flags="" # Extra flags to pass to dhcp client. > > #dhclient_flags_fxp0="" # Extra dhclient flags for fxp0 only > > -background_dhclient="YES" # Start dhcp client in the background. > > +background_dhclient="NO" # Start dhcp client in the background. > > #background_dhclient_fxp0="YES" # Start dhcp client on fxp0 in the > > background. > > synchronous_dhclient="NO" # Start dhclient directly on configured > > # interfaces during startup. > > Shouldn't synchronous_dhclient be ON by default then? The way it > is, DHCP is not used at all, I ended up with unreachable box which > didn't get any IP already.
Unless you have one of the few interfaces that does not generate link status events, dhclient will be started by devd. The only ones I know of are a subset set of ed(4) devices, though I think imp may have fixed those recently with a stub ifmedia interface. -- Brooks
pgp4YArOvvKk6.pgp
Description: PGP signature
