From owner-freebsd-questions@FreeBSD.ORG Mon May 31 13:35:14 2004 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 D856816A4CF for ; Mon, 31 May 2004 13:35:14 -0700 (PDT) Received: from wonkity.com (wonkity.com [65.173.111.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7ADEA43D1F for ; Mon, 31 May 2004 13:35:14 -0700 (PDT) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.12.11/8.12.11) with ESMTP id i4VKYUYk075171; Mon, 31 May 2004 14:34:30 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.12.11/8.12.11/Submit) with ESMTP id i4VKYUYE075168; Mon, 31 May 2004 14:34:30 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 31 May 2004 14:34:30 -0600 (MDT) From: Warren Block To: Scott In-Reply-To: <20040531191730.C0D563DDC@xprdmailfe12.nwk.excite.com> Message-ID: <20040531143126.K75154@wonkity.com> References: <20040531191730.C0D563DDC@xprdmailfe12.nwk.excite.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 4.8R sluggish performance 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: Mon, 31 May 2004 20:35:15 -0000 On Mon, 31 May 2004, Scott wrote: > I can always tell when the problem will occur based upon what > happens at boot. There are no error messages, but the slowness > begins when the standard daemons are loading. Cron and sshd > load just fine, but the delay occurs as sendmail loads, and > there is another delay as sendmail-clientmqueue loads. Once > that happens I know I'm in trouble thereafter. You can see if this is a DNS issue by comparing the reactions: ping hostname ping hostname's-ip-address In other words, if it's slow to look up a name, but quick when it doesn't have to, you've shown that it is a DNS problem. -Warren Block * Rapid City, South Dakota USA