Detection of permission changes

Kevin Korb kmk at
Thu Mar 1 19:04:50 MST 2012

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 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
2. --archive becomes the default and the current --no-* options are
turned into --* options to remove features that are currently in --archive
3. Rsync would have an option to print out a list of every file name
in the source tree and an explanation of why it was included or
excluded according to those rules
4. Rsync would have a syntax for absolute instead of relative paths
for includes and excludes (maybe //path/to/file)
5. I am almost tempted to say I would remove --checksum because 95% of
the times I have seen someone using it they did so to their own
detriment.  But I have seen at least 2 actual valid use cases for it
to exist so I would only add an extreme disclaimer to the man page
6. I would include --hard-links into --archive.  I know it can be a
memory hog but only if you have craploads of hard links and if you do
you can't possibly want to run without it.

Unfortunately I know that such fundamental changes would create a
backlash.  So maybe I wouldn't actually do them if I had the
authority.  But I am pretty sure they are all a good idea.

and of course now we are way beyond the scope of your question and
into the realm of the opinion of someone who has been using rsync as
the low level tool of a backup system for more than a decade and who
regularly helps out on #rsync.

On 03/01/12 20:50, Pavel Sanda wrote:
>> 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't print permission
> change on the terminal output by default. Since I was just testing
> the issue with dry-run it didn't occured to me that the is change
> is silently happening in the background.
> Pavel

- -- 
	Kevin Korb			Phone:    (407) 252-6853
	Systems Administrator		Internet:
	FutureQuest, Inc.		Kevin at  (work)
	Orlando, Florida		kmk at (personal)
	Web page:
	PGP public key available on web site.
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla -


More information about the rsync mailing list