Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Feb 2012 17:23:19 -0700 (MST)
From:      Warren Block <wblock@wonkity.com>
To:        Ian Lepore <freebsd@damnhippie.dyndns.org>
Cc:        freebsd-rc@freebsd.org
Subject:   Re: dhclient SYNCDHCP messiness
Message-ID:  <alpine.BSF.2.00.1202221701490.80831@wonkity.com>
In-Reply-To: <1329949733.1063.6.camel@revolution.hippie.lan>
References:  <alpine.BSF.2.00.1202220923030.77675@wonkity.com> <1329938748.21804.8.camel@revolution.hippie.lan> <alpine.BSF.2.00.1202221348360.79830@wonkity.com> <1329949733.1063.6.camel@revolution.hippie.lan>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 22 Feb 2012, Ian Lepore wrote:

> First, let me correct myself:  I *am* seeing exactly this glitch, I just
> hadn't noticed it until a few minutes ago when I rebooted and looked
> much more closely.
>
> Devd sees the link-up event because it sees all the events that happened
> before it started (for some definition of "all"; there's probably some
> reasonable list-length or buffer size limit somewhere).  I rebooted to
> test my vague memory on this... boot into single-user mode and manually
> run /sbin/devd -D and you'll see it processing the buffered events
> before daemonizing.  For some reason I had to mount / writeable before
> running devd in single-user or it failed.
>
> I now suspect (but haven't tested to confirm) that this message may be a
> side effect of r226345 which replaced some one-off pidfile logic in
> rc.d/dhclient with use of the standard rc_pid scheme, which is what is
> doing the whining.  I think the old one-off code to deal with the
> pidfile avoided whining in the 'quietstart' case.

Has r226345 been MFCed to 8-stable?  I only see it in head.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1202221701490.80831>