From owner-freebsd-questions@FreeBSD.ORG Sun Aug 23 07:10:46 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A426106568C for ; Sun, 23 Aug 2009 07:10:46 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (unknown [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 4285B8FC0C for ; Sun, 23 Aug 2009 07:10:46 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id n7N7Aj5E066467 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 23 Aug 2009 00:10:45 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id n7N7AjGK066466; Sun, 23 Aug 2009 00:10:45 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA07535; Sun, 23 Aug 09 00:09:04 PDT Date: Sun, 23 Aug 2009 00:12:44 -0700 From: perryh@pluto.rain.com To: nlandys@gmail.com Message-Id: <4a90ebec.IEQysCcW3m+S8CNF%perryh@pluto.rain.com> References: <560f92640908212137s376f1dc8vaba59618a6b71d67@mail.gmail.com> <20090822164219.1d439ae4@gumby.homeunix.com> <560f92640908221213p2e426650x3bcad3b93de4d4a3@mail.gmail.com> <560f92640908221226o5da22c8frae08de57520d98be@mail.gmail.com> <560f92640908221614vacd66ega4a56b79d3a59db6@mail.gmail.com> In-Reply-To: <560f92640908221614vacd66ega4a56b79d3a59db6@mail.gmail.com> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: /etc/rc.d/named dilemma X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Aug 2009 07:10:46 -0000 Nerius Landys wrote: > I am still bambuzzled by the network taking 30 seconds to come up. One thing I've run into recently is an Ethernet switch that needs to resolve spanning tree after a port reset. The physical link comes back up quickly, but it seems to take about 30 seconds before the switch will handle any traffic.