Re: Fwd: Hdup feature suggestion
Robert Haskins <rhaskins-X6DOoJyBSnRWk0Htik3J/[email protected]> Thu, 30 Sep 2004 09:09:12 -0400
| Newsgroups | gmane.comp.sysutils.backup.hdup.general |
|---|---|
| Message-ID | <[email protected]> |
Sorry, this wasn't clear. You just put ".nobackup" in the top level directory you don't want backed up. Each subdirectoy doesn't need the ".nobackup" file. Rather, all subdirectories will automatically *not* be backed up by tar. Robert Haskins wrote: > I believe hdup already does this. Just put an empty file (I use > ".nobackup") in each directory (including all subdirectories) you don't > want backed up. Then, add the name of the file you use to specify "no > backup" of the directory to the hdup.conf line like this: > > exclude = .nobackup, lost+found, /proc, /dev, /sys > > That should do what you want it to do, if I understand what you are asking. > > I see Miek's email saying that tar has issues with doing this. However, > it seems to work for me under FC1 and FC2 (with the stock FC tar) > without a problem. I have tested this (though not exhaustively) and "it > works for me". > > James Treworgy wrote: > >> (Sorry if you get this twice, I sent to frodo.miek.nl before an it >> appeared to bounce) >> >> Hi - I was just thinking it would be really nice to tell hdup to >> ignore a directory or directory heirarchy by placing a file actually >> in that directory, sort of like .htaccess. This would be useful >> because frequently I will put large files in a public location so >> people can download them, but I don't want them backed up. >> >> Rather than having to specifically configure hdup to exclude that >> directory for one time, it would be nice if I could add a file called >> ".hdup" which might contain a directive like "exclude=yes" or >> "exclude=yes, recurse=yes" to tell it to exclude this directory and >> all subdirectories. >> >> I suppose for this to work, hdup would need to scan the filesystem >> first and make a list of all directories to exclude. >> >> What do you think? >> >> Regards, >> >> James Treworgy >> >> >> > >