On Wed, Jul 30, 2014 at 10:26:11 -0400, Gene Heskett wrote:
> Ergo, a string "./lib/nfs/rpc_pipefs" isn't valid because it references 2
> more subdirs. And I have tried just "./rpc_pipefs", which, while it
> should be valid, did not work. And a simple ./lib make it skip about 50
> megs worth of stuff that lives in /var/lib, not to mention the whole /lib
> tree. Bad karma that.
(In the case of this specific directory, I think the problem you are
having is that the mount point is "/var/lib/nfs/rpc_pipefs" and not
"/lib/nfs/rpc_pipefs". [Tar's excludes are indeed processed relative to
the top of the DLE in question, but with that there's no restriction on
the number of subdirs in your exclude path...] But all that is a good
example of why excludes are the hard way to solve the "different
filesystem"-message issue....)
> Now, you mention NORMAL in the amgtar setup, so I have the man page on
> another screen right now. But the man page is not detailed enough to
> provide any hints on how to actually use it. ANY man page should at the
I looked at the amgtar man page for both Precise and Trusty (amanda
2.6.1 and 3.3.3, respectively), and both include an EXAMPLE section
showing a full example application declaration block. It's down near
the bottom of the document so perhaps you missed it when you were
reading the section for the NORMAL keyword, but I think it does provide
the usage hints you are seeking....
Nathan
----------------------------------------------------------------------------
Nathan Stratton Treadway - [email protected] - Mid-Atlantic region
Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
