From owner-freebsd-current@FreeBSD.ORG Tue Feb 17 22:50:23 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7BC1610656D2 for ; Tue, 17 Feb 2009 22:50:23 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.freebsd.org (Postfix) with ESMTP id F300D8FC1B for ; Tue, 17 Feb 2009 22:50:22 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.14.2/8.14.2) with ESMTP id n1HMoMtr018218 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 17 Feb 2009 17:50:22 -0500 (EST) X-DKIM: Sendmail DKIM Filter v2.5.3 duke.cs.duke.edu n1HMoMtr018218 Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id n1HLJLm7078123; Tue, 17 Feb 2009 16:19:21 -0500 (EST) (envelope-from gallatin) Date: Tue, 17 Feb 2009 16:19:21 -0500 From: Andrew Gallatin To: Mike Makonnen Message-ID: <20090217161921.A78099@grasshopper.cs.duke.edu> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <499A55AB.9080606@gmail.com>; from mmakonnen@gmail.com on Tue, Feb 17, 2009 at 09:13:40AM +0300 X-Operating-System: FreeBSD 4.9-RELEASE-p1 on an i386 Cc: Alexey Shuvaev , Garrett Cooper , FreeBSD Current Subject: Re: Annoyance with recent parallelism in rc.d X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2009 22:50:47 -0000 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