Sebastian,
I haven't used rrsync.
The --protect-args option causes file names to be sent over the socket, not
the command-line. So try removing that option. (One caveat: without that
option, spaces or special characters in the share name won't work since the
shell will try to interpret them, or split on spaces.)
Craig
On Mon, Aug 21, 2017 at 1:19 AM, Sebastian Schweizer <
sebast...@schweizer.tel> wrote:
> Hello,
>
> I started using BackupPC 4 a few days ago. It works great!
>
> Now I'm trying to setup a client with rrsync (restricted rsync) to allow
> only read access and only to some specific directories.
>
> The server uses the most recent release of rsync-bpc (3.0.9.8), and the
> client uses the most recent version of the rrsync script (which is from
> 2015-09-13, see [1]).
>
> I already found out that I have to remove 's' from $short_disabled in
> line 63, but it still does not work.
>
> The logs show:
>
> cmdExecOrEval: about to exec /usr/bin/rsync_bpc --bpc-top-dir
> /var/lib/backuppc --bpc-host-name my-client-host --bpc-share-name
> /something --bpc-bkup-num 14 --bpc-bkup-comp 3 --bpc-bkup-prevnum 13
> --bpc-bkup-prevcomp 3 --bpc-bkup-inode0 100 --bpc-attrib-new
> --bpc-log-level 1 -e /usr/bin/ssh\ -l\ myself --rsync-path=rsync --super
> --recursive --protect-args --numeric-ids --perms --owner --group -D
> --times --links --hard-links --delete --delete-excluded
> --one-file-system --partial --log-format=log:\ %o\ %i\ %B\ %8U,%8G\ %9l\
> %f%L --stats --timeout=72000 my-client-host:/something/ /
>
> /usr/local/bin/rrsync: invalid rsync-command syntax or options
>
> rsync_bpc: connection unexpectedly closed (0 bytes received so far)
> [Receiver]
>
>
> The SSH_ORIGINAL_COMMAND appears to be:
> rsync --server --sender -slHogDtprxe.iLsf
>
> What I find a bit weird is that the share name (/something) does not
> appear in that command that rsync_bpc sends to the client.
> When I use the normal rsync client (version 3.1.2 protocol version 31)
> and execute:
> $ rsync -a myself@my-client-host:/something /tmp/test
> then the SSH_ORIGINAL_COMMAND is:
> rsync --server --sender -logDtpre.iLsfxC . /something
>
> It appears that rrsync needs to read the "." argument in order to proceed.
>
> Does anyone know what else has to be changed in rrsync and/or rsync_bpc
> to get it working?
>
>
> Thanks!
> Sebastian
>
> [1] https://git.samba.org/?p=rsync.git;a=history;f=support/rrsync
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
