Re: Exclude patterns in tarsnaprc

[Bob Williams <linux@barrowhillfarm.org.uk>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/06/14 11:39, Warren Guy wrote:
> On 09/06/14 08:03, Bob Williams wrote:
>> If the leading slashes are stripped by tarsnap automatically,
>> then it probably doesn't matter whether I leave them in or not?
> 
> Stripped automatically by tarsnap from the backup path when doing
> the backup. So, your absolute exclude path `/home/foo*' won't match
> the backup path `home/foo_bar'.
> 
> However I could be mistaken. You could let us know?
> 
> Warren
> 
At first sight it seems to be respecting exclude options with a
leading '/', but I'm doing quite a big backup and getting bored with
watching the verbose output scroll through the terminal ;-)

I have 128 exclude options listed in tarsnap.conf. I'll report back
when it's finished and I can analyse what really happened.

Bob
- -- 
Bob Williams
System:  Linux 3.11.10-11-desktop
Distro:  openSUSE 13.1 (x86_64) with KDE Development Platform: 4.13.1
Uptime:  06:00am up 1 day 11:36, 5 users, load average: 0.00, 0.05, 0.19
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlOVk/wACgkQ0Sr7eZJrmU422ACfVam8Bjgsi/l7ovX7BhAjIypj
ofAAoKRUd4riGDyUsm13pObN33OmdxDw
=Y81D
-----END PGP SIGNATURE-----