From owner-freebsd-questions@FreeBSD.ORG Thu Aug 28 13:09:45 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39B7D16A4BF for ; Thu, 28 Aug 2003 13:09:45 -0700 (PDT) Received: from munk.nu (213-152-51-194.dsl.eclipse.net.uk [213.152.51.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 727A243FBD for ; Thu, 28 Aug 2003 13:09:44 -0700 (PDT) (envelope-from munk@munk.nu) Received: from munk by munk.nu with local (Exim 4.22) id 19sT5T-000HcB-Bl for questions@freebsd.org; Thu, 28 Aug 2003 21:09:43 +0100 Date: Thu, 28 Aug 2003 21:09:43 +0100 From: Jez Hancock To: questions@freebsd.org Message-ID: <20030828200943.GB66912@users.munk.nu> Mail-Followup-To: questions@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: User Munk Subject: Re: System very slow to boot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2003 20:09:45 -0000 On Thu, Aug 28, 2003 at 12:39:42PM -0400, Kevin.Greenidge1@VerizonWireless.com wrote: > 1) Since reloading my system I find that it is very slow to boot. It looks In addition to what others have said, note you can usually press 'ctrl-c' if the machine looks like it's taking a long time to load one of the rc scripts when you boot and that usually stops the execution of the current script. Generally though this does sound like a problem with DNS as other(s) have mentioned. I had a similar problem recently when my bandwidth provider went down for a day or two (ick) and sshd was taking a _long_ time to respond because it was trying to run a lookup on the inbound IP address when none of my resolving dns servers were available. First if you want to test things out, try disabling everything in /etc/rc.conf and re-enable them one by one until you find out what's causing the hang (similar with /usr/local/etc/rc.d scripts). If it does turn out to be sshd (suspect it may be)... Ensure your hostname is set correctly and fire up named on boot. The default named setup is pretty safe on freebsd and simply acts as a caching dns resolver. Then just make sure you have: nameserver 127.0.0.1 in /etc/resolv.conf. -- Jez http://www.munk.nu/