rsync - Sep 2011 - rsync over ssh with post-zfer

Hi,

I have install rsync version 3.0.8 on my FreeBSD server.

I've set it up so that I have to connect via ssh with key based
authentication.

The following is my rsyncd.conf file in my home directory on the server.

[ben-desktop]
use chroot = no
path = /home/bs/backups/ben-desktop/current
numeric ids = true
log file = /home/bs/backups/ben-desktop/rsync.log
list = true
read only = false
write only = false
post-xfer exec = /home/bs/post-xfer $RSYNC_MODULE_PATH

The file post-xfer file contains the following.

#!/bin/sh

env >> /var/log/prexfer_test.log
exit 0

I've added the following to the sudoers file so that the rsync daemon runs
as root and can preserve the file permissions.

bs ALL= NOPASSWD:/usr/local/bin/rsync

I use the following command from my client...

rsync -avz --rsync-path="sudo rsync" -e ssh rsync_test bs at
192.168.6.6:
:ben-desktop

When I run the command from my client it copies the files, keeping the
permissions, but it seems that the post-xfer command is not executed.

Should it work with my configuration?

Thanks

Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.samba.org/pipermail/rsync/attachments/20110909/91dfcf95/attachment.html>

On Fri, Sep 9, 2011 at 3:56 AM, Ben Short <ben at benshort.co.uk> wrote:
> The following is my rsyncd.conf file in my home directory on the server.
>
Since you are running rsync as root, the config file used will be
/etc/rsyncd.conf.  I assume that config file is simply missing the post-xfer
exec setting, unlike the one in the home dir.  If you want to use a
different config file, you'd have to pass in the --config=/some/rsyncd.conf
option to remote rsync.

I've added the following to the sudoers file so that the rsync daemon
runs
> as root and can preserve the file permissions.
>
> bs ALL= NOPASSWD:/usr/local/bin/rsync
>
It would be safer to force the whole "rsync --server --daemon ."
command via
sudoers so that a non daemon-server rsync cannot be run as root.  You may
also want to add a forced command to your ssh key in the authorized_keys
file so that that particular ssh key can only be used to startup a root
rsync server daemon.  If you go that route, you wouldn't need to use the
--rsync-path option on the client (since you would force sudo as part of the
command) and you could make the forced command specify any config file you
like (if you want to switch from the default global config).

..wayne..
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.samba.org/pipermail/rsync/attachments/20110909/45ba6e9e/attachment.html>