Date: Tue, 17 Feb 2009 16:19:21 -0500 From: Andrew Gallatin <gallatin@cs.duke.edu> To: Mike Makonnen <mmakonnen@gmail.com> Cc: Alexey Shuvaev <shuvaev@physik.uni-wuerzburg.de>, Garrett Cooper <yanefbsd@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Annoyance with recent parallelism in rc.d Message-ID: <20090217161921.A78099@grasshopper.cs.duke.edu> In-Reply-To: <499A55AB.9080606@gmail.com>; from mmakonnen@gmail.com on Tue, Feb 17, 2009 at 09:13:40AM %2B0300 References: <7d6fde3d0902150028n5f07ee55mc6026e1e4935eeb0@mail.gmail.com> <20090215153531.GA36438@wep4035.physik.uni-wuerzburg.de> <49998707.40205@gmail.com> <20090216210118.GA85984@wep4035.physik.uni-wuerzburg.de> <499A55AB.9080606@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Makonnen [mmakonnen@gmail.com] wrote: > 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. Maybe synchronous_dhclient=yes should be the default, as there are a lot of cases of it not working async? I had horribly annoying problems with NFS failing (via amd using NIS based maps) at boot on different machines 90% of the time. Some use bge, and others use nfe. At least in my case, there was no "reset". Eg: /dev/da0s2g: clean, 1992874 free (138 frags, 249092 blocks, 0.0% fragmentation) bge0: link state changed to DOWN Starting Network: lo0 bge0. bge1: link state changed to DOWN Setting date via ntp. 13 Feb 13:41:48 ntpdate[638]: no servers can be used, exiting Setting NIS domain: sw.myri.com. Starting rpcbind. /etc/rc: WARNING: failed to start amd Recovering vi editor sessions:. Setting synchronous_dhclient=yes seems to have fixed it for me. Drew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090217161921.A78099>