-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/06/14 08:01, Bob Williams wrote: > On 10/06/14 07:24, Colin Percival wrote: >> On 06/09/14 03: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? > >> The paths being backed up have leading / characters stripped. >> I'm pretty sure this happens before the paths are compared >> against exclude patterns. I'm pretty sure exclude patterns don't >> have leading / characters stripped. > >> ... if I'm misunderstanding what the code does, please let me >> know! > > Well, you should know. ;-) > > I think I'll strip all those leading '/' from my exclude patterns > before continuing with this backup. > > Bob > A quick comparison of my exclusion file with the results of
tarsnap -tv -f snapshot | less seems to show that exclusion patterns starting with '/' *are* respected; i.e. they work. HTH 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 2 days 11:36, 5 users, load average: 0.00, 0.05, 0.05 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlOWxzgACgkQ0Sr7eZJrmU4B/ACfbQlVBcC28EzlF1BDOMQAiGyK 9xkAnip5JRCSs1zssjgZzdjXeBi0Or6E =T6EH -----END PGP SIGNATURE-----
