From owner-freebsd-questions@FreeBSD.ORG Thu May 26 07:25:59 2005 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 D57A316A41C for ; Thu, 26 May 2005 07:25:59 +0000 (GMT) (envelope-from savage@savage.za.org) Received: from pyro.cenergynetworks.com (pyro.cenergynetworks.com [196.30.191.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id E359943D1F for ; Thu, 26 May 2005 07:25:57 +0000 (GMT) (envelope-from savage@savage.za.org) Received: from [127.0.0.1] (helo=pyro.cenergynetworks.com) by pyro.cenergynetworks.com with smtp (Exim 4.50) id 1DbChG-0000L7-r0 for freebsd-questions@freebsd.org; Thu, 26 May 2005 09:22:26 +0200 Received: from root by pyro.cenergynetworks.com with local (Exim 4.50) id 1DbChG-0000L3-qh for freebsd-questions@freebsd.org; Thu, 26 May 2005 09:22:26 +0200 Date: Thu, 26 May 2005 09:22:26 +0200 From: Chris Knipe To: freebsd-questions@freebsd.org Message-ID: <20050526072226.GA1141@savage.za.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.0.3.0, Antispam-Data: 2005.3.10.17 Subject: fsck on startup 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: Thu, 26 May 2005 07:26:00 -0000 Hi, I'm not sure what is causing this, but virtually -every- unclean system shutdown results in my server asking for the root password to run fsck manually, and this is a co-located server in a remote datacenter which I unfortunately can not get to as easily as I would want. Is there anyway to tell rc.conf or sysctl or anything else to get bsd to not pause for the root password??? Don't ask me why, but this has happened twice already now in one week that the system would for some reason just do a cold restart, and then sit at the startup waiting for the passwords.... This is 5.4-STABLE on a P4 3.4GHz 1GB Ram. -- Chris.