Linux – How to set destination permissions with rsync (chown chmod)

fedoralinuxrsync

I am trying to do a local rsync, from a mount point to a local folder. I need to set the owner, group, and permissions to specific settings. Here is what I am using:

 rsync -rtlv --chown=process:sambausers --chmod=D770,F770 /mnt/owncloud_mnt/Engineering/ /Drive_D/docs/Engineering_test

I end up with permissions 760 on both directories and files, and root:root on ownership (rsync is run as root).

What am I doing wrong?

TIA

Best Answer

rsync needs to be told that you want to set the permissions and owner/group information. It would be logical to assume that having --chmod or --chown would tell that but they don't.

For permissions to propagate you need the --perms or -p flag and for owner/group you need --owner --group or -og flags for the owner/group/permission information to be set.

The documentation is a bit unclearly written so it isn't clear how the permissions are handled with different combinations or if existing files are affected.

Related Solutions

Linux – Bash Script To Repair Directory and File Ownership

I think the way you are asking is kind of backwards. You don't want to take each folder and then find the user, rather you want to take the user and find their home folder.

#!/bin/bash
while IFS=':' read -r login pass uid gid uname homedir comment; do 
    echo chown $uid:$gid "$homedir"; 
done < /etc/passwd

You will need to remove the echo of course and you will need to run this with root permissions. I also always recommend a while loop instead of a for loop over ls myself. You can save this loop for doing anything with /etc/passwd.

Puppet – Managing Mounted Partitions with Fstab and Mount Points

You can tell Puppet not to manage a given metaparameter by setting it to undef.

file { "${location}/${name}":
    ensure                  => directory,
    owner                   => undef,
    group                   => undef,
    mode                    => undef,
    selinux_ignore_defaults => true,
}

In this event, if the directory doesn't exist before mounting, it will be created as the user and group which puppetd was started as (presumably root:wheel) and with a default umask. Puppet won't care about what these are set to at the time of creation or on any subsequent runs.

Alternatively, if you wanted to trade a little complexity for assurance, you could use a custom fact to determine what the active mounts are and a switch statement to set the directory permissions depending on whether it is pre- or post- mounted.

Best Answer

Related Solutions

Linux – Bash Script To Repair Directory and File Ownership

Puppet – Managing Mounted Partitions with Fstab and Mount Points

Related Topic