Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!usc!apple!agate!violet.berkeley.edu!izumi
From: izumi@violet.berkeley.edu (Izumi Ohzawa)
Newsgroups: comp.sys.next
Subject: Re: fsck messages on a reboot
Message-ID: <1989Dec10.223805.17331@agate.berkeley.edu>
Date: 10 Dec 89 22:38:05 GMT
References: <11993@phoenix.Princeton.EDU> <309@kgw2.UUCP>
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Organization: University of California, Berkeley
Lines: 22

>In article <11993@phoenix.Princeton.EDU>, lrr@Princeton.EDU (Lawrence R. Rogers) writes:
>> When the cube reboots, where do the messages from fsck go besides to the
>> console, which may not be visible?  Are they mirrored elsewhere for
>> later analysis? Thanks.

Boot messages to to /usr/adm/messages (anyway, I think most of them do),
along with a lot of messages the rest of the system generates.

Boy, there are many unnerving messages like "Window Server died ...
Cannot print..", which are apparently normal.

However, I don't think full fsck is performed on normal reboots
(if any), because boot messages say something like "filesystem clean --
skipping fsck ...".
I think there's probably a "filesystem dirty" flag in the
battery backed CMOS RAM which is cleared upon orderly shutdown, and
unless this bit indicates otherwise fsck is not done on subsequent
reboots.

Am I correct?

Izumi Ohzawa, izumi@violet.berkeley.edu