From owner-freebsd-questions@FreeBSD.ORG Tue Jan 31 17:39:07 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 CCE9B16A425 for ; Tue, 31 Jan 2006 17:39:07 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F0F543D79 for ; Tue, 31 Jan 2006 17:39:06 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id E21565C56; Tue, 31 Jan 2006 12:39:05 -0500 (EST) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 33719-02; Tue, 31 Jan 2006 12:39:05 -0500 (EST) Received: from [199.103.21.238] (pan.codefab.com [199.103.21.238]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 1FF815C16; Tue, 31 Jan 2006 12:39:05 -0500 (EST) In-Reply-To: <20060131172546.88150.qmail@web34003.mail.mud.yahoo.com> References: <20060131172546.88150.qmail@web34003.mail.mud.yahoo.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <636FF1E5-2930-4C92-8BEA-9F066213B15E@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Tue, 31 Jan 2006 12:39:04 -0500 To: manish jain X-Mailer: Apple Mail (2.746.2) X-Virus-Scanned: amavisd-new at codefab.com Cc: freebsd-questions@freebsd.org Subject: Re: Problem with fsck : continued 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: Tue, 31 Jan 2006 17:39:08 -0000 On Jan 31, 2006, at 12:25 PM, manish jain wrote: > So now the question is if I can get FreeBSD 6.0 to run fsck > automatically on restart in such a manner that all services come up > consistently. I am even willing to have fsck run in the foreground > upon EACH restart, irrespective of whether the previous shutdown > was proper or improper. How do I do this ? To start with, you could set: background_fsck="NO" ...in /etc/rc.conf to force filesystem checking to happen first. However, you are not going to have a very happy computing experience with any flavor of Unix if you keep shutting the system down uncleanly several times a day because of power failures. Try to obtain a UPS with a serial or USB connection and use a port like apcupsd to shut down cleanly... -- -Chuck