On Tue, Jul 05, 2005 at 11:19:09AM -0600, Graeme Humphries wrote:
>
> > In my experience the error occurs if Amanda can't access the directory
> > to see if the file is there.  Perhaps the docs need to be rephrased.
> 
> I'd rather just have any permission related error ignored if the
> optional keyword is used. Is there a situation where we *would* want it
> to hard error out on an optional exclude list if it can't get into the
> directory the exclude list is supposed to be in?


I'd have to peek at the docs/source to be certain of this,
but I haven't done so.

While runtar is setuid root, I don't think the pieces that
set up the runtar command line are run setuid root.  They
still need normal amanda user access to the exclude file.

If there were no exclude file, then the admin can reasonably
feel that it is not contributing to the list of excluded file.
Thus no error on setting optional is reasonable.

But what about an existing exclude file without access
permissions?  If that was not an error, how would the admin
know the exclude file was not contributing anything to the
list of excluded files??

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