US Robotics 7931 Podręcznik Użytkownika Pobierz pdf (Strona 93)

Chapter 3 Archiving 69

Archive Set Membership Conflicts

Sometimes the choice of path and other file characteristics for inclusion of a file in an

archive set results in ambiguous archive set membership. These situations are

resolved in the following manner:

1. The membership definition occurring first in the archive set is chosen.

2. Membership definitions local to a file system are chosen before any globally

defined definitions.

3. A membership definition that exactly duplicates a previous definition is noted as

an error.

Given these rules, more restrictive membership definitions should be placed earlier

in the directive file.

When controlling archiving for a specific file system (using the fs=fsname directive),

the archiver evaluates the file-system-specific directives before evaluating the global

directives. Thus, files can be assigned to a local archive set (including the

no_archive archive set) instead of being assigned to a global archive. This has

implications for global archive set assignments such as no_archive.

CODE EXAMPLE 3-15, it appears that the administrator did not intend to archive any

of the .o files across both file systems. However, because the local archive set

assignment allfiles is evaluated before the global archive set assignment

no_archive, the .o files in the samfs1 and samfs2 file systems are archived.

CODE EXAMPLE 3-16 shows the directives to use to ensure that no .o files are archived

in the two file systems.

CODE EXAMPLE 3-15 An archiver.cmd File With Possible Membership Conflicts

no_archive . -name .*\.o$

fs = samfs1

allfiles .

fs = samfs2

allfiles .

CODE EXAMPLE 3-16 Corrected archiver.cmd File

fs = samfs1

no_archive . -name .*\.o$

allfiles .

fs = samfs2

no_archive . -name .*\.o$

allfiles .

1 2 ... 88 89 90 91 92 93 94 95 96 97 98 ... 287 288

Brak uwag

US Robotics 7931 Podręcznik Użytkownika Strona 93