Checking the system after a crash
Several programs are used to maintain the
integrity of the Authentication database,
the system area of the filesystem, and the filesystem as a whole.
When checking or fixing problems,
the rule is to work from the most basic components of the filesystem
outward. Otherwise, corrections made at the higher levels may be undone by
programs fixing the lower levels. Given this, use these programs
after a system crash or abnormality in this order:
-
Run a
filesystem check
with
fsck(ADM).
This occurs automatically at reboot after a crash.
-
Check for the absence of critical files
with
tcbck(ADM).
This is automatic at reboot time.
-
Recheck the consistency of the Authentication database
with
authck(ADM).
-
Verify system software as described in
``Verifying software''.
This will check and repair problems with file permissions, including the
repair of broken symbolic links.
-
Generate an audit report (optional).
Next topic:
Using the override terminal
Previous topic:
The authentication database files
© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003