On Wed, Mar 12, 2003 at 01:27:32PM +0100, Paul Slootman
wrote:> This is a patch against the manpage to clarify what the --perm option
> does and does not do.
If we are going to embellish this description it would be
good to make it clear that the behavior of rsync in this
regard is the same as that of cp.
Most of those complaining about this behavior fail to
understand it is consistent with cp, scp, rcp et al.
If i may suggest...
This option causes rsync to update the permissions
of existing destination files to be the same as the
source files. Like other file copy utilities new
destination files will receive the same permissions
as their source files.
>
>
> Paul Slootman
> diff -ru orig/rsync-2.5.6/rsync.1 rsync-2.5.6/rsync.1
> --- orig/rsync-2.5.6/rsync.1 2003-01-28 04:11:57.000000000 +0100
> +++ rsync-2.5.6/rsync.1 2003-03-07 12:18:19.000000000 +0100
> @@ -562,8 +562,13 @@
> default\&.
> .IP
> .IP "\fB-p, --perms\fP"
> -This option causes rsync to update the remote
> -permissions to be the same as the local permissions\&.
> +This option causes rsync to update the destination file's
> +permissions to be the same as the source's permissions\&.
> +Whether or not this option is specified, destination permissions for
> +newly created files are ALWAYS the same as the source permissions\&.
> +I.e. this option only affects whether the permissions on existing
> +destination files are updated or not\&.
> +
> .IP
> .IP "\fB-o, --owner\fP"
> This option causes rsync to set the owner of the
> --
> To unsubscribe or change options:
http://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt