On Tue, Mar 11, 2003 at 10:48:01AM -0800, Rob Helmer wrote:
> On Mon, Mar 10, 2003 at 07:55:31PM -0500, Jon LaBadie wrote:
> > On Mon, Mar 10, 2003 at 03:53:03PM -0800, Rob Helmer wrote:
> > > Is there any way I can have one exclude.gtar for /, and one
> > > for /usr/local ? For example, I may want /etc and not
> > > /usr/local/etc, or vice versa and the exclude list would
> > > look at both as an entry for "etc".
> > 
> > From amanda.conf:
> > 
> > #    If a relative pathname is specified as the exclude list,
> > #    it is searched from within the directory that is
> > #    going to be backed up.
> > 
> > Thus, each DLE can have its own exclude file.
> 
> Oh, ok, so you specify the path to the exclude list relative
> to the dir specified to be backed up, e.g. 
> 
> /export/home/exclude.gtar
> /exclude.gtar
> 
> And have this as a disklist :
> 
> # hostname      diskdevice      dumptype        spindle interface
> server          /               normal          0
> server          /export/home    normal          0
> 
> And each client specified the exclude list in their amanda.conf like so :

Clients don't have amanda.conf's.  But ...

> exclude list "./exclude.gtar"
> 
> Am I reading that correctly?

... that is correct.
> 

If you are doing it as you describe, you could have one global "exclude list"
in the server's amanda.conf.  Otherwise I think you can have separate entries
in any dumptype.  So if there is a special need, like you are forbidden to
have any extraneous files in the root dir of an entry, you could have a
dumptype for that disklist entry that shows an exclude list file elsewhere.

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)