Re: the nodump option and excluding files?

2016-06-05 Thread Colin Percival
On 06/05/16 08:25, Graham Percival wrote:
> Unfortunately, nodump only refers to single files.

... or directories.  Not useful in this case, I just don't want the mailing
list archives to be unclear about this.

-- 
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid


Re: the nodump option and excluding files?

2016-06-05 Thread Graham Percival
Unfortunately, nodump only refers to single files.  If you want to exclude
every single instance of .DS_Store, then you would either need to set nodump
on every single .DS_Store file on your computer, or use the "exclude" method.
My apologies for giving you imprecise advice earlier.

Instead, I suggest adding this to your tarsnap config file:

exclude */.DS_Store

Also, some filesystems are case sensitive.  I think that OSX is not
case-sensitive, but just in case, the first DS S are in upper case, while the
other letters are lower-case: DS_Store, not ds_store.

Cheers,
- Graham

On Fri, Jun 03, 2016 at 11:15:06PM -0700, Sarah Alawami wrote:
> Hello to all. I tried to do the nodump option, however I cannot get it to 
> work on files. I want to exclude every instant let's say of ds_store. I get 
> how to exclude directories and I hope that works, but when I do a dry-run 
> even though i have the flags set on what I thought was ds_store I still see 
> it in the dry run.
> 
> I followed the examples given at this message link from the list.
> 
> http://mail.tarsnap.com/tarsnap-users/msg00961.html
> 
> I know that is a bit old but I was hoping it would help. I did this.
> 
> Chflags nodump .ds_store
> And that seemed to work except I still see .ds_store at the dry run when I 
> but the terminal output. What am I not understanding here? I thought it was 
> global so I would put --nodump in my script which I did, but so far no joy.
> 
> Blessings to all, and happy Friday