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:

1. Run a filesystem check with fsck(ADM). This occurs automatically at reboot after a crash.

2. Check for the absence of critical files with tcbck(ADM). This is automatic at reboot time.

3. Recheck the consistency of the Authentication database with authck(ADM).
   
   
   
   

4. Verify system software as described in ``Verifying software'' in the SCO OpenServer Handbook. This will check and repair problems with file permissions, including the repair of broken symbolic links.

5. Generate an audit report (optional).