I agree that the space escaping of the rsync -e part looks like the
issue. However, if that is indeed the case, I am surprised no one had
stumbled on this before.
The RsyncSshArgs are added to the rsyncArgs like other parts. Here's the
relevant code snippet in lib/BackupPC/Xfer/Rsync.pm:124 an
My guess is, that the -e parameter needs all ssh parameters included as
a value. That is what the escaped spaces IMHO does. E.g. whole
"/usr/bin/ssh\ -l\ ubuntu\ -C\ -c\ aes256-...@openssh.com" is single
value for -e.
It might be a feature of the rsync_bpc. I am not sure, how this works
with regul
Yes,
Multiple lines:
Running: /usr/local/bin/rsync_bpc --bpc-top-dir /var/lib/backuppc
--bpc-host-name test.i.molnix.com --bpc-share-name / --bpc-bkup-num 1
--bpc-bkup-comp 0 --bpc-bkup-prevnum -1 --bpc-bkup-prevcomp -1
--bpc-bkup-inode0 75573 --bpc-attrib-new --bpc-log-level 1 -e /usr/bin/ss
In the logs, you can see actual commands issued. Have you compared those?
Cheers,
Jan
On 14/01/2019 10:17, Johan Ehnberg wrote:
>
> Hello,
>
> I stumbled upon this weirdness when benchmarking offloadable SSH
> ciphers using the rsync transfer method.
>
> In short, splitting up the RsyncSshArgs I
Hello,
I stumbled upon this weirdness when benchmarking offloadable SSH ciphers
using the rsync transfer method.
In short, splitting up the RsyncSshArgs I use on multiple lines fails:
'-e',
'$sshPath -l ubuntu',
'-C',
'-c aes256-...@openssh.com'
and combining them on one line works (but
