I have an odd problem. I'm running the following rsync command as root:
[code]
rsync -v -r -t --delete --partial /OHPRSstorage/Acronis/workstations/ /mnt/localBackup/Acronis/workstations
[code]
a source file on /OHPRSstorage/Acronis/workstations/common/is:
but after the rsync command the permissions are:
root's umask is 0022

Why is rsync not creating the destination files with og+r per its umask?

That's how umask works. It only removes permissions, it doesn't add them. You might consider revisiting some basic Unix tutorials?

What is it that you want it to do? If you want to replicate all file permissions, user/group ownership etc, then vrt flags alone won't do it. If that's your goal, then try the following flags:

-vaxAX --delete --partial

1 members found this post helpful.

Good info IsaacKuo !

And if one uses and wants to preserve their HardLinks, then maybe add the -H flag as well:

All these flags inply you'll be running as root ...

and as always:
HTH

-- kjh

1 members found this post helpful.

Yes, it looks like the -a flag is needed here to get the expected results. Or at least the -p option is needed to save permissions and it is included in the -a option.

1 members found this post helpful.

I don't think I agree with this statement. If I have umask 0022 and I `touch` a file, I get -rw-r--r--. In other words, it creates the file with o+r. It seems to me that rsync is *creating* files on the target directory (on the same computer) and in the absence of specify permissions it should create with the 0022 umask (but of course, it's not).

I've found a solutions, but neither the -a nor -p option are what I want. If you'll notice in my OP the source file permissions were -rw-rw----, meaning that -a or -p would keep those permission and I still wouldn't have o+r. To do this, I use:
The 'D' flag is special and indicated setting 'x' for directories.

This works, but still doesn't explain why rsync doesn't use the user's umask to create the target files (if -a -p or --chmod are not specified). I guess that's just the way rsync works, so I'll not worry about it.

1 members found this post helpful.

The umask is applied against whatever permissions the calling program requests. For new files, most programs, including touch, request 0666, so with a umask of 0022 the result is 0644. (Compilers that produce executable files generally request 0777.) The permissions that rsync requests for a new file are those of the source file, in this case 0660, and the result is 0640. The "-p" flag just causes rsync to ignore the umask and copy the source permissions exactly. Unless you use "--chmod", rsync never adds permissions that the source file did not have.

2 members found this post helpful.

Good to know. Thanks.