On Sat, 24 May 2003 itohy@netbsd.org wrote:

: 	This is probably because fsck is not a direct child process
: 	of the /etc/rc shell.
: 	Do not use rcorder and invoke fsck directly
: 	from the root /etc/rc shell.

Does renaming /etc/rc.d/fsck to /etc/rc.d/fsck.sh fix the problem?  (This
will make the contents of /etc/rc.d/fsck.sh run as direct children of the
startup shell.)

-- 
-- Todd Vierling <tv@pobox.com>