Hello Christoph,
we (upstream author and me) can't reproduce this bug.
...
rsnapshot make no use of scp, we are not sure why it is used in your
setup. Do you have a special environment (special ssh version, some
restrictions with ssh), a forced command in your authorized_keys file
on the remote host or something like that?
You are right on this. I found the other trigger to the problem:
The remote user ([EMAIL PROTECTED]) which rsync/rsnapshot authenticates
against, had /usr/bin/scponly (v4.0-1) as his shell. Changing the the
shell to /bin/sh makes the problem go away.
Please also try to run the rsync command manually, cause maybe this
error is not caused by rsnapshot.
The examples I gave, where run manually. It was the exact statement as
generated by the rsnapshot script.
Given this new information, I guess this is more an rsync bug/feature,
and has nothing to do with rsnapshot?
(I posted an update on this on rsync bug 158170; it was during
troubleshooting my problems with that bug, that I was experimenting with
the timeout option.)
Serge
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
