Re: Detection of permission changes

2012-03-02 Thread Kevin Korb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I can see --checksum being faster on a slow link. This is because - --ignore-times has to send more checksums than --checksum does. This is why more data was transferred even though no files were actually transferred. On 03/02/12 12:57, Joachim Otah

Re: Detection of permission changes

2012-03-02 Thread Joachim Otahal (privat)
Nope. Available line speed: Sending 5 MBit, receiving 6 MBit. "real" line speed - well, it is a VPN over Internet, very "controlled" speed.. All files are already sync. Fileset: about 3.31 GB, 3146 files, several runs. min time/max time/mean time rsync -rtvvzPc --compress-level=9 --fuzzy

Re: Detection of permission changes

2012-03-02 Thread Kevin Korb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Try --ignore-times instead of --checksum. It will appear to do more since it will actually re-delta xfer everything but in my experience that is faster than --checksum almost all of the time. On 03/02/12 02:07, Joachim Otahal (privat) wrote: > Kevin

Re: Detection of permission changes

2012-03-01 Thread Joachim Otahal (privat)
Kevin Korb schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am not much of a programmer so I know I could never take over rsync development but if I could boss such people around here are the new directions I would take: 1. --itmize-changes is eliminated and becomes part of --verbose

Re: Detection of permission changes

2012-03-01 Thread Kevin Korb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yeah, I know that there is an inherent resistance to changing behavior but IMO --verbose is utterly useless without --itemize-changes. There is simply no reason to provide a list of transferred file names and nothing else about them. I am not much of

Re: Detection of permission changes

2012-03-01 Thread Pavel Sanda
> First, you should almost always use -t unless you have a really good > reason to not sync timestamps otherwise future rsync runs will not > know what has changed and what hasn't. Sure, thats my default. > Finally, when in doubt, --itemize-changes. This was the right hint, thanks ;) rsync doesn

Re: Detection of permission changes

2012-03-01 Thread Kevin Korb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 First, you should almost always use -t unless you have a really good reason to not sync timestamps otherwise future rsync runs will not know what has changed and what hasn't. Second, when you run with -p rsync should detect and fix any permission diff

Detection of permission changes

2012-03-01 Thread Pavel Sanda
Hi, is rsync supposed to detect permission change only (if other attributes are equal at both source and target)? I'm able to synchronize permissions by -p when the file changes (e.g. its timestamp when -t is used) but otherwise the sole permission change of the file (e.g. via chmod u-w file) re