A/UX: How to Check for Files without Changing Them (8/94)


In attempting to check for the presence of a file without correcting any errors, an A/UX user tried the following command from the SASH (Stand Alone Shell) application's command line:

esch -v -b -f

This command automatically corrected a permissions error on a file.

(Editor's Note: SASH is equivalent to the A/UX 3.0 Startup shell.)

The reason is that "escher" begins the autorecovery process. It does generate a report when it discovers a file that does not match the rules in the CML (Configuration Master List). It also updates the CML but it will not tell you what was updated.

For instance, "escher" does not distinguish between changed permissions and changed contents. It only asks if you want to update the autorecovery file system with each changed file. It also does not create checksums for files.
For this reason, use of escher is discouraged.

The "-m" option would probably be better if you do not wish to answer all the questions. This option merely mails a list of updated and missing files.

Refer to the A/UX Local System Administration manual section on "Managing Disks" for details about the use of autorecovery.


Article Change History:
24 Aug 1994 - Reviewed and updated.

Support Information Services


Published Date: Feb 18, 2012