On Sun, Jan 15, 2006 at 03:55:33PM +0100, Josef Wolf wrote:
> On Sat, Jan 14, 2006 at 03:04:26PM -0500, Jon LaBadie wrote:
> > > In the above case the DLE in question was the root-directory.  In
> > > filesystem semantics "/media" and "./media" is aequivalent as long as
> > > you are cd'd into / (as it was in this case).
> > 
> > Not that it explains any of Josef's problems, but I think some are
> > confusing the contents of an exclude list file (the things being excluded)
> > and the specified name of the exclude list file.
> 
> I am using amanda for almost 15 years now (IIRC), and I have fallen into
> this trap several times.
> 
> > The contents of the file must always be specified as relative to the
> > head directory of the DLE.
> 
> This sentence should find its way into the man page to clarify this topic.
> 
> > The name of the list file can be specified absolute (full) or relative.
> > If relative it is relative to the head directory of the DLE.  If absolute,
> > it is based on the client's root directory.
> 
> OK, this is already in the man-page.
> 
> > Thus you could have a global exclude list file affecting all DLE's on
> > the client plus DLE specific exclude lists.
> 
> Beware of a trap here:  For example assume you want to exclude /bin because
> you can always re-install it from your distribution CD/DVD.  And then you
> set /usr/local on a separate DLE.  Now your /usr/local/bin will be excluded,
> too.
> 

That is exactly how I use it.  Each of my 4 holding disks has the same
initial directory name ("dumps") and is at the root of a file system.
My global exclude file contains "./dumps", "./tmp", and "./temp".

> Therefore, with the current implementation of the exclude mechanism, I
> would strongly recommend a separate exclude file for every DLE.
> 

Different strokes :)

-- 
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)