Thanks to you, and all that pointed this out.
The strange thing about it, is that our exclusion worked fine until we
upgraded our gnutar from 1.12.? to 1.13.19
So the "problems with restoring" with 1.13 alluded to on the amanda-patches
page are pretty well obsolete by .19 ?
"John R. Jackson" wrote:
> >now: our exclude.gtar doesnt work properly, i.e. if we are backing up
> >filesystem w mount point: /fs
> >then an entry like /fs/somedirectory is not excluded.
>
> Amanda runs GNU tar in the directory you put in disklist, so the exclusion
> entry needs to be relative to that, i.e. "./somedirectory".
>
> I always have trouble with exclusion patterns. Here's a little script
> to test them in the same way Amanda uses GNU tar:
>
> ftp://gandalf.cc.purdue.edu/pub/amanda/gtartest-exclude
>
> >I have seen on the amanda-patches page that there are problems with gnu
> >tar 1.13
> >" with exclude patterns and restoring"
>
> I think that's referring literally to version "1.13" of GNU tar, which
> seems to appear on this list from time to time. If you're already past
> that at 1.13.19, you should be in good shape.
>
> >3) If there are showstopper problems with 1.13, then perhaps someone has
> >patches to 1.12 to get it to backup files > 2 gig on solaris 2.6
> >(actually we should be going to solaris 8 soon)
>
> This is GNU tar related, not Amanda related, but I think I remember
> playing with it at one time and the basic idea was to add whatever:
>
> getconf LFS_CFLAGS
>
> reports to your compile lines and whatever:
>
> getconf LFS_LDFLAGS
> getconf LFS_LIBS
>
> reports to the load/link line. I'm pretty sure this got gzip going,
> but tar may have other issues since it knows a lot more about files.
>
> Using 1.13.19 is, without doubt, the much easier approach.
>
> >shanna leonard
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
--
----
MHO
---
shanna leonard
arizona health sciences library
626-2923
----------------------------------
