Graeme Humphries wrote:

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?

Amanda will not complain
- if the exclude file on the client is not there at all
  In this case amanda can construct a gtar argument list that does
  not contain the exclude list of a non-existing file.
- or if the file is not readable: in that case amanda trusts the
  suid-root runtar executable so that gnutar can read the contents of
  the file, never mind the permissions.

But Amanda does need to verify if the file is there or not, otherwise
gnutar will complain about having handed a nonexisting file in the
argument list.


--
Paul Bijnens, Xplanation                            Tel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM    Fax  +32 16 397.512
http://www.xplanation.com/          email:  Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...    *
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out          *
***********************************************************************