ADSM-L

Re: exclude syntax frustration

2002-01-04 21:07:00
Subject: Re: exclude syntax frustration
From: Dylan Ryback <dryback AT HOME DOT COM>
Date: Fri, 4 Jan 2002 19:05:12 -0700
I'm no expert on the subject, but check out the section on Creating an
Include-Exclude List at the following link:

http://www.tivoli.com/support/public/Prodman/public_manuals/td/TSMC/SH26-412
2-02/en_US/HTML/index.html

Do you have an include statement at the bottom of the options file that is
getting matched first?  Remember that the file is processed from the bottom
up.  Here's a snippet on how the options file is processed:
The client program processes the include and exclude options as follows:

  1.. Files are checked; directories are only checked if the exclude.dir
option is specified.
  2.. File names are compared to the include-exclude list from the bottom
up. When a match is found, the processing stops and checks whether the
option is include or exclude. If the option is include, the file is backed
up. If the option is exclude, the file is not backed up.
  3.. If a match is not found, files listed are implicitly included and
backed up.
  4.. If policy administration is in effect, files are backed up according
to the default management class, or the management class you specify on a
matching include option.
The following examples demonstrate bottom up processing.


  Example 1
  Assume that /home is defined as the domain, and you defined the following
statements for the include and exclude options:
   exclude *.obj
   include /home/foo/.../*.obj
   exclude /home/foo/junk/*.obj

  The file being processed is: /home/foo/dev/test.obj. Processing follows
these steps:

    1.. Rule 3 (the last include or exclude statement defined) is checked
first because of bottom up processing. The file /home/foo/junk/*.obj does
not match the file name that is being processed.
    2.. Processing moves to Rule 2 and checks. This time, file
/home/foo/.../*.obj matches the file name that is being processed.
Processing stops, the option is checked, and it is include.
    3.. File /home/foo/dev/test.obj is backed up.

  Example 2
  Assume that /home is defined as the domain, and you defined the following
statements for the include and exclude options:
   exclude *.obj
   include /home/foo/.../*.obj
   exclude /home/foo/junk/*.obj

  The file being processed is: /home/widg/copyit.bat. Processing follows
these steps:

    1.. Rule 3 is checked and finds no match.
    2.. Rule 2 is checked and finds no match.
    3.. Rule 1 is checked and finds no match.
    4.. Because a match is not found, file /home/widg/copyit.bat is
implicitly included and backed up.

  Example 3
  Assume that /home is defined as the domain, and that you defined the
following statements for the include and exclude options:
   exclude /.../*.obj
   include /home/foo/.../*.obj
   exclude /home/foo/junk/*.obj

  The current file being processed is: /home/lib/objs/printf.obj. Processing
follows these steps:

    1.. Rule 3 is checked and finds no match.
    2.. Rule 2 is checked and finds no match.
    3.. Rule 1 is checked and a match is found.
    4.. Processing stops, the option is checked, and it is exclude.
    5.. File /home/lib/objs/printf.obj is not backed up.

<Prev in Thread] Current Thread [Next in Thread>