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.

esch(8) esch(8)<br />

Autorecovery file systems contain copies of files that are necessary<br />

for a minimal multiuser A/UX system. If new versions of<br />

comm<strong>and</strong>s, programs, or files are installed on the system, the autorecovery<br />

file systems should be Updated using eu(<strong>1M</strong>) or<br />

eseher(IM).<br />

eseh will check each file system for bad blocks. This is done by<br />

verifying that each block can be read. If possible, any blocks that<br />

cannot be read will be spared by the hardware or replaced with alternate<br />

blocks (see al tblk(4» by the software. If neither of<br />

these is successful, the block number is added to a list of blocks<br />

that is passed to fsck. fsek will add these blocks to a file associated<br />

with inode one; this has the effect of removing the blocks<br />

from the file system. Checking for bad blocks is a timeconsuming<br />

process. This phase of autorecovery may be omitted<br />

using the -b flag option. It is advisable to occasionally run eseh<br />

without the -b flag option to be sure any bad blocks have been<br />

dealt with in the appropriate manner.<br />

eseh will then run fsek on each file system. This invocation of<br />

fsek uses the -y flag option. All questionable files will be removed<br />

from the file system. If fsek should fail or if the superblock<br />

is unreadable, a mkfs (see mkfs(IM» will be performed<br />

on the file system.<br />

After the file systems have been checked for consistency, e s eh<br />

will enter the file check merge phase. The configuration master<br />

list (see eml(4» is a list of files required for a multiuser NUX<br />

system. This file gives rules about the attributes of each required<br />

file. The file check merge phase of e s eh will check each file in<br />

the eml for conformity to the specified file attributes (size, version,<br />

check sum, permissions, <strong>and</strong> so forth). If a file does not conform<br />

to these rules, eseh will attempt to replace it with a copy<br />

from an autorecovery file system. If the file in question is found<br />

on an autorecovery file system, it must conform to the eml rules<br />

or it will not be placed on the root or usr file system.<br />

FILES<br />

/ete/esehatology/init2files<br />

SEE ALSO<br />

eseher(IM), eu(IM), eupdate(<strong>1M</strong>), fsck(<strong>1M</strong>), mkfs(IM),<br />

altblk(4), eml(4), dpme(4), fs(4), autoreeovery(8),<br />

StartupShell(8).<br />

"<strong>System</strong> Startup <strong>and</strong> Shutdown" inAIUX Local <strong>System</strong> Adminis-<br />

2<br />

February, 1990<br />

RevisionC

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

Saved successfully!

Ooh no, something went wrong!