Date: Sun, 22 Feb 2009 07:57:23 -0800 From: Garrett Cooper <yanefbsd@gmail.com> To: pyunyh@gmail.com Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Annoyance with recent parallelism in rc.d Message-ID: <7d6fde3d0902220757m3ae95f11t72bec63d4f568d4@mail.gmail.com> In-Reply-To: <7d6fde3d0902220545u1f6f042do71aeab9d8428a847@mail.gmail.com> References: <7d6fde3d0902150028n5f07ee55mc6026e1e4935eeb0@mail.gmail.com> <20090217011358.GC23900@michelle.cdnetworks.co.kr> <7d6fde3d0902220545u1f6f042do71aeab9d8428a847@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 22, 2009 at 5:45 AM, Garrett Cooper <yanefbsd@gmail.com> wrote:
> On Mon, Feb 16, 2009 at 5:13 PM, Pyun YongHyeon <pyunyh@gmail.com> wrote:
>> 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
>>
>> Would you try attached patch? I don't like the patch but it may
>> reduce number of link state change message generated by dhclient.
>>
>>> for parallelism at startup rc.d it can't properly detect dependencies
>>> with some cases like NFS mounts?
>>>
>>> Thanks,
>>> -Garrett
>
> Sorry.. got caught up with work work again and forgot about this email.
>
> I'll try this patch out after debugging another issue and get back to
> you within the hour.
>
> Thanks!
> -Garrett
Both the patch and the workaround fixed my problems, but
unfortunately the patch alone doesn't fix the problem so my guess is
what needs to happen is the dhcp_client needs to be dependent of all
of the other network services. Do we have something like an rc.network
setup properly for this?
Thanks,
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d0902220757m3ae95f11t72bec63d4f568d4>