Re: Annoyance with recent parallelism in rc.d

On Sun, Feb 15, 2009 at 12:28:20AM -0800, Garrett Cooper wrote:
> I just updated my world to a recent snapshot (a build from last week)
> and I'm noting some parallelism / backgrounding which is really
> causing issues with my NIC and NFS mounts. I had to hit CTRL-D 5 times
> in order to get the system to come up because it couldn't resolve my
> NFS server's hostname, because the NIC wasn't up and going yet (as it
> uses the DHCP client in background mode due to the new default).
> 
> Now I realize that this all ties back into the issue with the NIC
> (which I've approached Pyun about, and which I appreciate his help is
> solving issues with this buggy chipset), but is there really a need
> for  parallelism at startup rc.d it can't properly detect dependencies
> with some cases like NFS mounts?
> 
Me too.
I have ntpd failing to resolve dns names.
I have noticed this since appr. 1.350 of etc/defaults/rc.conf (12 days ago).
I was hoping this will go away...

Commit log:
SVN rev 188010 on 2009-02-02 15:38:24Z by mtm

Since, rc.d/defaultroute has the ability to wait for a
default route to show up we can turn this knob back on
without screwing subsequent daemons that expect to be
able to talk to the outside world.

^^^^^^^^^^^^^^^^^^^^^^^^^^^
Seems it is not the case...
Interesting: setting background_dhclient="NO" does not
solve the issue. Maybe something else was changed?
My current 'workaroud' is synchronous_dhclient="YES"

My hardware:
~> uname -a
FreeBSD wep4035 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sat Feb 14 01:29:05 CET 2009     root_at_wep4035:/usr/obj/usr/src/sys/NOUSB  amd64

mskc0_at_pci0:1:0:0:       class=0x020000 card=0x81f81043 chip=0x436411ab rev=0x12 hdr=0x00
    vendor     = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
    device     = '88E8056 Yukon PCI-E Gigabit Ethernet Controller'
    class      = network
    subclass   = ethernet

msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=11a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4>
        ether 00:1f:c6:89:83:ec
	[snip]
        media: Ethernet autoselect (100baseTX <full-duplex,flag0,flag1>)
        status: active

Alexey.