rsync: on remote machine: --drop-cache: unknown option

2011-03-11 Thread will trillich
We've been using RSYNC to back things up and it's sick nasty wicked awesome. Recently we migrated our receiving server to a different machine (Debian lenny) and now we're running into this DROP-CACHE: UNKNOWN OPTION error: sender-machine$ *rsync -Cvaz -e ssh --delete --exclude blah/ --exclude yad

Re: Backing up resource forks

2011-03-11 Thread Wayne Davison
On Thu, Mar 10, 2011 at 10:50 PM, Y z wrote: > A little research showed me that rsync (2.6.9) for Mac supports the -E > option, which is supposed to back up the resource forks, too. > That is an option that apple added, but it is not implemented very well and is not compatible with non-apple rsy

Re: rsync: on remote machine: --drop-cache: unknown option

2011-03-11 Thread Wayne Davison
On Fri, Mar 11, 2011 at 6:44 AM, will trillich wrote: > rsync: on remote machine: --drop-cache: unknown option > That is not an official rsync option, so check the patches that were applied. It shouldn't send the option to the other rsync without you using --drop-cache, so either the patch is b

Re: Backing up resource forks

2011-03-11 Thread David Allie
Check out rsync.samba.org and download/compile version 3.0.7. Very stable, I've been downloading/compiling my own rsync from here for several years and have not encountered any problems. If you're interested and would like the download/compile steps, let me know. Mike Bombich (CCC, Apple) used

Re: Backing up resource forks

2011-03-11 Thread Mike Bombich
FWIW, I updated http://www.bombich.com/rsync.html just recently with a minor bug fix to my HFS+ compression patch (preserving resource forks when --fileflags was not used). (And I do not work for Apple :-) Mike On Mar 11, 2011, at 9:34 AM, David Allie wrote: > Check out rsync.samba.org and do

Re: Backing up resource forks

2011-03-11 Thread David Allie
Mike, thanks for the clarification and for updating your instructions. -- David On Mar 11, 2011, at 11:05 AM, Mike Bombich wrote: FWIW, I updated http://www.bombich.com/rsync.html just recently with a minor bug fix to my HFS+ compression patch (preserving resource forks when --fileflags was not

Re: Backing up resource forks

2011-03-11 Thread alex conway
THATS GREAT. ALL I NEED NOW IS CREDIT DEBIT DETAILS TO PROVE YOUR I.D On Fri, Mar 11, 2011 at 4:13 PM, David Allie wrote: > Mike, thanks for the clarification and for updating your instructions. > > -- David > > *On Mar 11, 2011, at 11:05 AM, Mike Bombich wrote:* > FWIW, I updated http://www.bo

Unintuitive backwards-incompatible behaviour with rsync -a --link-dest --size-only

2011-03-11 Thread Bryan Hoyt | Brush Technology
I use rsync to backup my system, using a command-line such as the following: > rsync [src] [dst] -a --link-dest --size-only In this case, [src] is produced by a command that makes no attempt to preserve timestamps ("svnadmin hotcopy", in this case). That's why I use --size-only. Here's the rub: i

two bugs in rsync 3.0.6 - ampersands in filenames, double quoting required

2011-03-11 Thread travis+ml-rsync
1) deleting path/to/(Something) Word Word Anotherword--Word Word.pdf IO error encountered -- skipping file deletion I think either the -- is causing it to fail, or more likely, the next filename, which it didn't bother to print out, which has an ampersand in the name, causes it to fail. I am usi

maybe a Unicode problem? was Re: two bugs in rsync 3.0.6 - ampersands in filenames, double quoting required

2011-03-11 Thread travis+ml-rsync
On Fri, Mar 11, 2011 at 06:41:26PM -0800, travis+ml-rs...@subspacefield.org wrote: > deleting path/to/(Something) Word Word Anotherword--Word Word.pdf > IO error encountered -- skipping file deletion > > I think either the -- is causing it to fail, or more likely, the next > filename, which it di

Re: maybe a Unicode problem? was Re: two bugs in rsync 3.0.6 - ampersands in filenames, double quoting required

2011-03-11 Thread travis+ml-rsync
On Fri, Mar 11, 2011 at 07:00:57PM -0800, travis+ml-rs...@subspacefield.org wrote: > This time it failed when trying to delete a file containing the word > G\#303\#266del > > I wonder if there's some issues with Unicode... Or possibly not. This time, the last line before the I/O error was a fi