Date: Wed, 22 Feb 2012 12:25:48 -0700 From: Ian Lepore <freebsd@damnhippie.dyndns.org> To: Warren Block <wblock@wonkity.com> Cc: freebsd-rc@freebsd.org Subject: Re: dhclient SYNCDHCP messiness Message-ID: <1329938748.21804.8.camel@revolution.hippie.lan> In-Reply-To: <alpine.BSF.2.00.1202220923030.77675@wonkity.com> References: <alpine.BSF.2.00.1202220923030.77675@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2012-02-22 at 11:40 -0700, Warren Block wrote: > In /etc/rc.conf: > > ifconfig_em0="SYNCDHCP" > > dhclient runs on startup, then later tries to run again: > > Starting dhclient. > em0: no link ... > . > . > got link > (...) > Starting Network: lo0 em0. > (...) > Starting devd. > Starting ums0 moused > . > dhclient already running? (pid=344). > Creating and/or trimming log files > > So is this from /etc/network.subr starting dhclient because the > interface is set to DHCP, then /etc/rc.d/dhclient running directly > later? > > This is with > > FreeBSD lightning 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Tue Feb 21 22:25:30 MST 2012 > root@lightning:/usr/obj/usr/src/sys/LIGHTNING i386 > _______________________________________________ > freebsd-rc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-rc > To unsubscribe, send any mail to "freebsd-rc-unsubscribe@freebsd.org" >From the sequence of things there it looks like the second invocation may be from a devd rule, but I thought all the standard rules used "dhclient quietstart" and that one of the effects of that was to supress the "already running" warning. I updated a couple systems to 8.3-{PRERELEASE,BETA1} over the past few days and I haven't seen such a glitch. I don't think it should make a difference, but I use synchronous_dhclient=YES and ifconfig_foo=DHCP -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1329938748.21804.8.camel>