From owner-freebsd-hackers  Fri May 19 06:57:39 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id GAA23034
          for hackers-outgoing; Fri, 19 May 1995 06:57:39 -0700
Received: from haven.ios.com (haven.ios.com [198.4.75.45])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA23027
          for <hackers@freebsd.org>; Fri, 19 May 1995 06:57:38 -0700
Received: (from rashid@localhost) by haven.ios.com (8.6.11/8.6.9) id KAA05940 for hackers@freebsd.org; Fri, 19 May 1995 10:00:09 -0400
From: "Rashid Karimov." <rashid@haven.ios.com>
Message-Id: <199505191400.KAA05940@haven.ios.com>
Subject: fsck & boot Q
To: hackers@FreeBSD.org
Date: Fri, 19 May 1995 10:00:08 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1323      
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

	Hi there folx,


	Albeit it works just great here ( server has ~3.000 accounts )
	and is _very fast and stable in sense of load average ( it
	doesn't fluctuate between 2-20 as on SS10 here ) , sometimes
	it does reboot w/o kernel being able to determine the reason
	and panic. Just silent and sporadic reboot. The mileage of
	uptime can vary - between 10 -3 days.
	Since the FreeBSD kernel is rather a good cather of ordinary
	problems ( on other computer here , from different vendor it 
	never ever rebooted w/o panic being activated and reason explained ),
	I suspect there is some magic'n'stupid conflict somewhere deep
	inside of that Gateway p90/PCI Bt946c/128Mb RAM/Diamond Viper
	juke box.

	Well, but the Q is :
	when it reboots in this way , it cleans all the filesystem
	except one , and then prompts for the default shell and asks
	sysadm to clean the FS manually.And if noone is available - 
	the system just sits there forever.
	Is there any way to explicitly tell the system to run fsck -y
	_automatically on all FSes or at least on those it can't clean

	out ? And after everything is cool - just resume normal operation ?
	If it's impossible - can some1 point me to the code which is involved
	in that stage of boot process ? 


	Rashid


	-=-=- Come,come Monday !=-=-=-=
	-=-=- Bring us 2.0.5 :) -=-=-=-