Date: Tue, 17 Feb 2009 09:14:03 +0300 From: Mike Makonnen <mmakonnen@gmail.com> To: Alexey Shuvaev <shuvaev@physik.uni-wuerzburg.de> Cc: Garrett Cooper <yanefbsd@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Annoyance with recent parallelism in rc.d Message-ID: <499A55AB.9080606@gmail.com> In-Reply-To: <20090216210118.GA85984@wep4035.physik.uni-wuerzburg.de> References: <7d6fde3d0902150028n5f07ee55mc6026e1e4935eeb0@mail.gmail.com> <20090215153531.GA36438@wep4035.physik.uni-wuerzburg.de> <49998707.40205@gmail.com> <20090216210118.GA85984@wep4035.physik.uni-wuerzburg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexey Shuvaev wrote: > Rev. 1.4 of rc.d/defaultroute. > Ok, what should I do to have network daemons happy on startup? > I am on a LAN so always have plugged-in cable. > I do see on the console: > msk0: link state changed to DOWN > msk0: link state changed to UP > got link > msk0: link state changed to DOWN > Starting Network: lo0 msk0. > msk0: link state changed to UP > msk0: link state changed to DOWN > > AFAIK some NIC (or PHY-s?) require some sort of reset to handle some > events. > Should I live with synchronous_dhclient="YES" or something else? This seems to be an issue with the driver for the network card. No special handling needs to take place in rc.d. So, yes, synchronous_dhclient=yes should be the appropriate work-around. Cheers. -- Mike Makonnen | GPG-KEY: http://people.freebsd.org/~mtm/mtm.asc mtm @ FreeBSD.Org | AC7B 5672 2D11 F4D0 EBF8 5279 5359 2B82 7CD4 1F55 FreeBSD | http://www.freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?499A55AB.9080606>