Re: --chmod for destination only

What I'm concerned with is the fact that --chmod -p will create new copies of files in the destination rather than create links Matt McCutchen wrote: > On Fri, 2009-02-06 at 09:32 -0500, Matthew Monaco wrote: >> Is it possible to set the permissions on the destination side? As I

--chmod for destination only

Is it possible to set the permissions on the destination side? As I understand it, --chmod just pretends certain permissions are coming from the sending side. I'd like to be able to set permissions to readonly in the destination while coming from a --copy/link-dest which may more may not have had

--link-dest, update permissions w/o creating a new file

I like the behavior of first doing: cp -al /backup/old /backup/new rsync /source /backup/new This way permissions will be updates throughout all snapshots (I really don't want multiple copies of my entire music collection if I decide to make all songs group readable... etc) Has anyone come up wit

Re: --no-whole-file ineffective

no way to get --stats per file? Matt McCutchen wrote: > On Fri, 2008-11-21 at 13:56 -0500, Matthew Monaco wrote: >> I've set the --no-whole-file flag on a number of different transfers, >> but it does not appear to do anything. Even if I change one character >> in a

--no-whole-file ineffective

I've set the --no-whole-file flag on a number of different transfers, but it does not appear to do anything. Even if I change one character in a long text file, --progress indicates that the entire size of the file has been sent. Matt -- Please use reply-all for most replies to avoid omitting th

are hardlinks supported when rsyncing over ssh?

Subject should be enough: are hardlinks supported when rsyncing over ssh? I know that I cannot do anything with hardlinks if I'm using SSHFS over FUSE, I was wondering if rsync is plagued by the same problem. Matt -- Please use reply-all for most replies to avoid omitting the mailing list. To un

Re: How to delete files older than X on backup during sync?

You can do something like "rsync OPTIONS --rsync-path="find /root-dir/ -mtime +14 -delete ; rsync" SRC DEST" although, to be safe you'll probably want something like: "rsync OPTIONS --rsync-path="find /root-dir/ -type f -mtime +14 -delete ; rsync" --prune-empty-dirs SRC DEST" I'm not sure wheth

feature suggestion: no-backup filter modifier

I think a modifier for filter rules that inhibits the --backup option for the particular line might be useful. for example I could have --filter='H,nb /.mozilla/firefox/x.default/Cache' or I could have --filter'+ /Documents' --filter'+,nb /.mozilla' (So my documents will be backed up to --b

exclude vs hide

What is the difference between exclude and hide in the filter rules? -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.htm

Thorough distributed backup/sync strategy

Does anyone have a good distributed backup strategy? I've been revising mine for a year or so now and always realize there's some hole or another in it. I get the feeling to do it exactly the way I want it needs to be complex, but I'm looking for something elegant. My data consists of some of th

switch for hardlink behavior on destination

Is there a way to control how rsync handles hardlinks on the destination? For example: I have two directories on a remote system which each have the same hardlink called TestFile.txt I use only one folder as the destination and TestFile.txt needs to be updated. Can I choose to preserve the hard

Re: Re: rsync backup permissions

So would the receiving end need to be running in daemon mode? There would be no way to set the proper ownership if it isn't? Matt McCutchen wrote: > On Thu, 2008-10-09 at 14:38 +0100, michael wrote: >> On Thu, 2008-10-09 at 14:17 +0100, michael wrote: >>> I wish to use rsync to backup users' home

Re: --link-dest behavior

check if the destination connected to via ssh and then run the cp command over SSH (which is a different cp command than it normally would be because the ssh commands are relative to the users home directory...) Matt McCutchen wrote: > On Fri, 2008-10-03 at 01:14 -0400, Matthew Monaco wrote: >

--link-dest behavior

Greetings All, I've been thinking about the current behavior of the --link-dest=DIR option. In the absence of --delete, ALL members of DIR should be linked to the destination (aside from those that are changed). If not, there should at least be a --no-link-dest-delete option. (This latter optio