From owner-freebsd-rc@FreeBSD.ORG Mon Feb 20 11:07:14 2012 Return-Path: Delivered-To: freebsd-rc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46C97106567A for ; Mon, 20 Feb 2012 11:07:14 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 347DB8FC28 for ; Mon, 20 Feb 2012 11:07:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1KB7Eqq090230 for ; Mon, 20 Feb 2012 11:07:14 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1KB7DJC090228 for freebsd-rc@FreeBSD.org; Mon, 20 Feb 2012 11:07:13 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 20 Feb 2012 11:07:13 GMT Message-Id: <201202201107.q1KB7DJC090228@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-rc@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-rc@FreeBSD.org X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Feb 2012 11:07:14 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o conf/164393 rc [rc.d] restarting netif with static addresses doesn't o conf/163508 rc [rc.subr] [patch] Add "enable" and "disable" commands o conf/163488 rc Confusing explanation in defaults/rc.conf o conf/163321 rc [rc.conf] [patch] allow _fib syntax in rc.conf o conf/162642 rc .sh scripts in /usr/local/etc/rc.d get executed, not s p kern/161899 rc [route] ntpd(8): Repeating RTM_MISS packets causing hi o conf/161107 rc [rc] stop_boot in mountcritlocal usage is incorrect. o conf/160403 rc [rc] [patch] concurrently running rc-scripts during bo o conf/160240 rc rc.d/mdconfig and mdconfig2 should autoset $_type to v o conf/159846 rc [rc.conf] routing_stop_inet6() logic doesn't handle ip o conf/158557 rc [patch] /etc/rc.d/pf broken messages o conf/158127 rc [patch] remount_optional option in rc.initdiskless doe o conf/153666 rc [rc.d][patch] mount filesystems from fstab over zfs da o conf/153200 rc post-boot /etc/rc.d/network_ipv6 start can miss neighb o conf/153123 rc [rc] [patch] add gsched rc file to automatically inser o conf/150474 rc [patch] rc.d/accounting: Add ability to set location o o conf/149867 rc [PATCH] rc.d script to manage multiple FIBS (kern opti o conf/149831 rc [PATCH] add support to /etc/rc.d/jail for delegating Z o conf/148656 rc rc.firewall(8): {oip} and {iip} variables in rc.firewa o conf/147685 rc [rc.d] [patch] new feature for /etc/rc.d/fsck o conf/147444 rc [rc.d] [patch] /etc/rc.d/zfs stop not called on reboot o conf/146053 rc [patch] [request] shutdown of jails breaks inter-jail o conf/145445 rc [rc.d] error in /etc/rc.d/jail (bad logic) o conf/145399 rc [patch] rc.d scripts are unable to start/stop programs o conf/145009 rc [patch] rc.subr(8): rc.conf should allow mac label con o conf/144213 rc [rc.d] [patch] Disappearing zvols on reboot o conf/143637 rc [patch] ntpdate(8) support for ntp-servers supplied by o conf/143085 rc [patch] ftp-proxy(8) rc(8) with multiple instances o conf/142973 rc [jail] [patch] Strange counter init value in jail rc o conf/142434 rc [patch] Add cpuset(1) support to rc.subr(8) o conf/142304 rc rc.conf(5): mdconfig and mdconfig2 rc.d scripts lack e o conf/141909 rc rc.subr(8): [patch] add rc.conf.d support to /usr/loca o conf/141907 rc [rc.d] Bug if mtu (maybe others?) is set as first argu o conf/141678 rc [patch] A minor enhancement to how /etc/rc.d/jail dete o conf/141275 rc [request] dhclient(8) rc script should print something o conf/140440 rc [patch] allow local command files in rc.{suspend,resum o conf/140261 rc [patch] Improve flexibility of mdconfig2 startup scrip o conf/138208 rc [rc.d] [patch] Making rc.firewall (workstation) IPv6 a o conf/137629 rc [rc.d] background_dhclient rc.conf option causing doub o conf/137470 rc [PATCH] /etc/rc.d/mdconfig2 : prioritize cli parameter o conf/137271 rc [rc.d] Cannot update /etc/host.conf when root filesyst o conf/136624 rc [rc.d] sysctl variables for ipnat are not applied on b o conf/135338 rc [rc.d] pf startup order seems broken [regression] o conf/134918 rc [patch] rc.subr fails to detect perl daemons o conf/134660 rc [patch] rc-script for initializing ng_netflow+ng_ipfw o conf/134333 rc PPP configuration problem in the rc.d scripts in combi o conf/134006 rc [patch] Unload console screensaver kernel modules if s o conf/133890 rc [patch] sshd(8): add multiple profiles to the rc.d scr o conf/132483 rc rc.subr(8) [patch] setfib(1) support for rc.subr o conf/128299 rc [patch] /etc/rc.d/geli does not mount partitions using o conf/126392 rc [patch] rc.conf ifconfig_xx keywords cannot be escaped p bin/126324 rc [patch] rc.d/tmp: Prevent mounting /tmp in second tim o conf/124747 rc [patch] savecore can't create dump from encrypted swap o conf/124248 rc [jail] [patch] add support for nice value for rc.d/jai o conf/123734 rc [patch] Chipset VIA CX700 requires extra initializatio o conf/123222 rc [patch] Add rtprio(1)/idprio(1) support to rc.subr(8). o conf/123119 rc [patch] rc script for ipfw does not handle IPv6 o conf/122968 rc [rc.d] /etc/rc.d/addswap: md swapfile multiplication a o conf/122477 rc [patch] /etc/rc.d/mdconfig and mdconfig2 are ignoring o conf/122170 rc [patch] [request] New feature: notify admin via page o o kern/121566 rc [nfs] [request] [patch] ethernet iface should be broug o conf/120406 rc [devd] [patch] Handle newly attached pcm devices (eg. o conf/119874 rc [patch] "/etc/rc.d/pf reload" fails if there are macro o conf/119076 rc [patch] [rc.d] /etc/rc.d/netif tries to remove alias a o bin/118325 rc [patch] [request] new periodic script to test statuses o conf/118255 rc savecore never finding kernel core dumps (rcorder prob o conf/117935 rc [patch] ppp fails to start at boot because of missing o conf/113915 rc [patch] ndis wireless driver fails to associate when i o conf/109980 rc /etc/rc.d/netif restart doesn't destroy cloned_interfa o conf/108589 rc rtsol(8) fails due to default ipfw rules o conf/106009 rc [ppp] [patch] [request] Fix pppoed startup script to p o conf/105689 rc [ppp] [request] syslogd starts too late at boot o conf/105145 rc [ppp] [patch] [request] add redial function to rc.d/pp o conf/104549 rc [patch] rc.d/nfsd needs special _find_processes functi o conf/102700 rc [geli] [patch] Add encrypted /tmp support to GELI/GBDE o conf/99721 rc [patch] /etc/rc.initdiskless problem copy dotfile in s o conf/99444 rc [patch] Enhancement: rc.subr could easily support star o conf/96343 rc [patch] rc.d order change to start inet6 before pf o conf/93815 rc [patch] Adds in the ability to save ipfw rules to rc.d o conf/92523 rc [patch] allow rc scripts to kill process after a timeo o conf/89870 rc [patch] [request] make netif verbose rc.conf toggle o conf/88913 rc [patch] wrapper support for rc.subr o conf/85819 rc [patch] script allowing multiuser mode in spite of fsc o kern/81006 rc ipnat not working with tunnel interfaces on startup o conf/77663 rc Suggestion: add /etc/rc.d/addnetswap after addcritremo o conf/73677 rc [patch] add support for powernow states to power_profi o conf/58939 rc [patch] dumb little hack for /etc/rc.firewall{,6} o conf/56934 rc [patch] rc.firewall rules for natd expect an interface o conf/44170 rc [patch] Add ability to run multiple pppoed(8) on start 89 problems total. From owner-freebsd-rc@FreeBSD.ORG Wed Feb 22 19:08:35 2012 Return-Path: Delivered-To: freebsd-rc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0BC4106566B for ; Wed, 22 Feb 2012 19:08:35 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 9433F8FC18 for ; Wed, 22 Feb 2012 19:08:35 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q1MIeLot079002 for ; Wed, 22 Feb 2012 11:40:21 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q1MIeLcK078999 for ; Wed, 22 Feb 2012 11:40:21 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Wed, 22 Feb 2012 11:40:21 -0700 (MST) From: Warren Block To: freebsd-rc@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Wed, 22 Feb 2012 11:40:21 -0700 (MST) Subject: dhclient SYNCDHCP messiness X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2012 19:08:35 -0000 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 From owner-freebsd-rc@FreeBSD.ORG Wed Feb 22 19:39:01 2012 Return-Path: Delivered-To: freebsd-rc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68762106564A for ; Wed, 22 Feb 2012 19:39:01 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from qmta13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [76.96.27.243]) by mx1.freebsd.org (Postfix) with ESMTP id 4F06E8FC08 for ; Wed, 22 Feb 2012 19:39:01 +0000 (UTC) Received: from omta23.emeryville.ca.mail.comcast.net ([76.96.30.90]) by qmta13.emeryville.ca.mail.comcast.net with comcast id d72T1i00B1wfjNsAD7RrGB; Wed, 22 Feb 2012 19:25:51 +0000 Received: from damnhippie.dyndns.org ([24.8.232.202]) by omta23.emeryville.ca.mail.comcast.net with comcast id d7Rq1i00T4NgCEG8j7Rq1d; Wed, 22 Feb 2012 19:25:51 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id q1MJPmij005117; Wed, 22 Feb 2012 12:25:48 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) From: Ian Lepore To: Warren Block In-Reply-To: References: Content-Type: text/plain; charset="us-ascii" Date: Wed, 22 Feb 2012 12:25:48 -0700 Message-ID: <1329938748.21804.8.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-rc@freebsd.org Subject: Re: dhclient SYNCDHCP messiness X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2012 19:39:01 -0000 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 From owner-freebsd-rc@FreeBSD.ORG Wed Feb 22 21:09:00 2012 Return-Path: Delivered-To: freebsd-rc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7FCF1065674 for ; Wed, 22 Feb 2012 21:08:59 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id A35168FC0C for ; Wed, 22 Feb 2012 21:08:59 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q1ML8u2R079957; Wed, 22 Feb 2012 14:08:56 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q1ML8unu079954; Wed, 22 Feb 2012 14:08:56 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Wed, 22 Feb 2012 14:08:56 -0700 (MST) From: Warren Block To: Ian Lepore In-Reply-To: <1329938748.21804.8.camel@revolution.hippie.lan> Message-ID: References: <1329938748.21804.8.camel@revolution.hippie.lan> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Wed, 22 Feb 2012 14:08:56 -0700 (MST) Cc: freebsd-rc@freebsd.org Subject: Re: dhclient SYNCDHCP messiness X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2012 21:09:00 -0000 On Wed, 22 Feb 2012, Ian Lepore wrote: > 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 > > 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. The devd rule triggers on a link up event. This is an em(4) card that does not do the multiple up/down events on start like an re(4) card. But easy to test. ...And interestingly enough, commenting out lines 51-56 of devd.conf stops the double call: DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 10.0.0.1 bound to 10.0.0.8 -- renewal in 300 seconds. Starting Network: lo0 em0. lo0: flags=8049 metric 0 mtu 16384 options=3 inet 127.0.0.1 netmask 0xff000000 em0: flags=8843 metric 0 mtu 9216 options=9b ether 00:02:b3:a9:93:d7 inet 10.0.0.8 netmask 0xffffff00 broadcast 10.0.0.255 media: Ethernet autoselect (1000baseT ) status: active Starting devd. Starting ums0 moused . Creating and/or trimming log files For completeness, there's an unconnected re(4) card built into the motherboard that shows "re0: link state changed to DOWN" immediately after the "Starting devd." message. AFAIK, it should happen like this: ifconfig em0 em0 changes to up dhclient em0 (sync) wait until em0 gets a DHCP lease or fails devd (em0 is already up, devd should do nothing) So I guess the question is: why is devd seeing a link up event there? > 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 That's a good point: testing... nope, it does the same thing as "SYNCDHCP". From owner-freebsd-rc@FreeBSD.ORG Wed Feb 22 22:28:57 2012 Return-Path: Delivered-To: freebsd-rc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E4301065678 for ; Wed, 22 Feb 2012 22:28:57 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from qmta02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [76.96.30.24]) by mx1.freebsd.org (Postfix) with ESMTP id 323EE8FC08 for ; Wed, 22 Feb 2012 22:28:56 +0000 (UTC) Received: from omta21.emeryville.ca.mail.comcast.net ([76.96.30.88]) by qmta02.emeryville.ca.mail.comcast.net with comcast id d9wW1i0041u4NiLA2AUwGQ; Wed, 22 Feb 2012 22:28:56 +0000 Received: from damnhippie.dyndns.org ([24.8.232.202]) by omta21.emeryville.ca.mail.comcast.net with comcast id dAUv1i00T4NgCEG8hAUvYR; Wed, 22 Feb 2012 22:28:56 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id q1MMSs53005227; Wed, 22 Feb 2012 15:28:54 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) From: Ian Lepore To: Warren Block In-Reply-To: References: <1329938748.21804.8.camel@revolution.hippie.lan> Content-Type: text/plain; charset="us-ascii" Date: Wed, 22 Feb 2012 15:28:53 -0700 Message-ID: <1329949733.1063.6.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-rc@freebsd.org Subject: Re: dhclient SYNCDHCP messiness X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2012 22:28:57 -0000 On Wed, 2012-02-22 at 14:08 -0700, Warren Block wrote: > On Wed, 22 Feb 2012, Ian Lepore wrote: > > > 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 > > > > 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. > > The devd rule triggers on a link up event. This is an em(4) card that > does not do the multiple up/down events on start like an re(4) card. > But easy to test. ...And interestingly enough, commenting out lines > 51-56 of devd.conf stops the double call: > > DHCPREQUEST on em0 to 255.255.255.255 port 67 > DHCPACK from 10.0.0.1 > bound to 10.0.0.8 -- renewal in 300 seconds. > Starting Network: lo0 em0. > lo0: flags=8049 metric 0 mtu 16384 > options=3 > inet 127.0.0.1 netmask 0xff000000 > em0: flags=8843 metric 0 mtu 9216 > options=9b > ether 00:02:b3:a9:93:d7 > inet 10.0.0.8 netmask 0xffffff00 broadcast 10.0.0.255 > media: Ethernet autoselect (1000baseT ) > status: active > Starting devd. > Starting ums0 moused > . > Creating and/or trimming log files > > For completeness, there's an unconnected re(4) card built into the > motherboard that shows "re0: link state changed to DOWN" immediately > after the "Starting devd." message. > > AFAIK, it should happen like this: > > ifconfig em0 > em0 changes to up > dhclient em0 (sync) > wait until em0 gets a DHCP lease or fails > devd (em0 is already up, devd should do nothing) > > So I guess the question is: why is devd seeing a link up event there? > > > 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 > > That's a good point: testing... nope, it does the same thing as > "SYNCDHCP". > > 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. -- Ian From owner-freebsd-rc@FreeBSD.ORG Thu Feb 23 00:23:22 2012 Return-Path: Delivered-To: freebsd-rc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CB5A106566B for ; Thu, 23 Feb 2012 00:23:22 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 1B1728FC12 for ; Thu, 23 Feb 2012 00:23:21 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q1N0NJBa081037; Wed, 22 Feb 2012 17:23:19 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q1N0NJqb081034; Wed, 22 Feb 2012 17:23:19 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Wed, 22 Feb 2012 17:23:19 -0700 (MST) From: Warren Block To: Ian Lepore In-Reply-To: <1329949733.1063.6.camel@revolution.hippie.lan> Message-ID: References: <1329938748.21804.8.camel@revolution.hippie.lan> <1329949733.1063.6.camel@revolution.hippie.lan> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Wed, 22 Feb 2012 17:23:19 -0700 (MST) Cc: freebsd-rc@freebsd.org Subject: Re: dhclient SYNCDHCP messiness X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2012 00:23:22 -0000 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. From owner-freebsd-rc@FreeBSD.ORG Thu Feb 23 01:24:21 2012 Return-Path: Delivered-To: freebsd-rc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB087106566C for ; Thu, 23 Feb 2012 01:24:21 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by mx1.freebsd.org (Postfix) with ESMTP id 8DA1E8FC08 for ; Thu, 23 Feb 2012 01:24:21 +0000 (UTC) Received: from omta15.emeryville.ca.mail.comcast.net ([76.96.30.71]) by qmta03.emeryville.ca.mail.comcast.net with comcast id dC0A1i0021Y3wxoA3DQMbZ; Thu, 23 Feb 2012 01:24:21 +0000 Received: from damnhippie.dyndns.org ([24.8.232.202]) by omta15.emeryville.ca.mail.comcast.net with comcast id dDQL1i0054NgCEG8bDQLlf; Thu, 23 Feb 2012 01:24:21 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id q1N1OI6i005390; Wed, 22 Feb 2012 18:24:18 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) From: Ian Lepore To: Warren Block In-Reply-To: References: <1329938748.21804.8.camel@revolution.hippie.lan> <1329949733.1063.6.camel@revolution.hippie.lan> Content-Type: text/plain; charset="us-ascii" Date: Wed, 22 Feb 2012 18:24:18 -0700 Message-ID: <1329960258.1095.4.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-rc@freebsd.org Subject: Re: dhclient SYNCDHCP messiness X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2012 01:24:21 -0000 On Wed, 2012-02-22 at 17:23 -0700, Warren Block wrote: > 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. Apparently so, in r231278. Maybe you're not seeing what you expect because there was some glitch with the way the merge was done, which I totally didn't understand when I saw the commit mail and replies -- I'm just starting to learn svn so I didn't get all the implications of that thread. -- Ian From owner-freebsd-rc@FreeBSD.ORG Sat Feb 25 20:17:02 2012 Return-Path: Delivered-To: freebsd-rc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 62827106564A for ; Sat, 25 Feb 2012 20:17:02 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 1BEA78FC12 for ; Sat, 25 Feb 2012 20:17:01 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q1PKGx3H005088; Sat, 25 Feb 2012 13:16:59 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q1PKGxES005085; Sat, 25 Feb 2012 13:16:59 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sat, 25 Feb 2012 13:16:59 -0700 (MST) From: Warren Block To: Ian Lepore In-Reply-To: <1329960258.1095.4.camel@revolution.hippie.lan> Message-ID: References: <1329938748.21804.8.camel@revolution.hippie.lan> <1329949733.1063.6.camel@revolution.hippie.lan> <1329960258.1095.4.camel@revolution.hippie.lan> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Sat, 25 Feb 2012 13:16:59 -0700 (MST) Cc: freebsd-rc@freebsd.org Subject: Re: dhclient SYNCDHCP messiness X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2012 20:17:02 -0000 On Wed, 22 Feb 2012, Ian Lepore wrote: >> Has r226345 been MFCed to 8-stable? I only see it in head. > > Apparently so, in r231278. Maybe you're not seeing what you expect > because there was some glitch with the way the merge was done, which I > totally didn't understand when I saw the commit mail and replies -- I'm > just starting to learn svn so I didn't get all the implications of that > thread. For reference, http://svnweb.freebsd.org/base?view=revision&sortby=rev&revision=231278 And this is the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=165477