02.07.2013 Views

A/UX® System Administrator's Reference Sections 1M, 7, and 8

A/UX® System Administrator's Reference Sections 1M, 7, and 8

A/UX® System Administrator's Reference Sections 1M, 7, and 8

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

escher(IM) escher(IM)<br />

When escher is given a list of filenames, it will create an entry<br />

in the CML list for each file <strong>and</strong> copy it to the autorecovery file<br />

systems. The filenames must be full pathnames, beginning with /.<br />

The CML entry will have simple rules as described above. The<br />

named files should be files that are not currently in the CML <strong>and</strong><br />

do not reside in autorecovery file systems.<br />

FILES<br />

/etc/escher<br />

/etc/eschatology/init2files<br />

SEE ALSO<br />

cml(4), dpme(4), fs(4), nvram(7), autorecovery(8).<br />

DIAGNOSTICS<br />

The diagnostic messages are intended to be self-explanatory.<br />

If an autorecovery file system runs out of space while escher is<br />

copying new files to it, escher will not attempt to update any of<br />

the other files contained in that file system. escher will display<br />

a message that indicates the file system is full.<br />

WARNINGS<br />

When escher is given a list of files to be added to the CML, the<br />

user must include the directories the files reside in. In order for a<br />

file to be restored through autorecovery, all the directories in the<br />

pathname of a file must also be in the CML list.<br />

escher requires that the CML file be sorted by filename.<br />

February, 1990<br />

Revision C<br />

3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!