If you host allows scripting in PHP or similar and does not have it locked down so extra processes can not be execed by user scripts, then you could try starting rsync in listening mode that way.

Running rsync as a publicly addressable service (rather than indirectly via SSH or similar) is not generally recommended for non-public data though. If you have some way of running long-lived listening processes on the host you could try starting rsync manually listening for connections on a non-privileged port, but most techniques for doing that would require proper shell access via SSH too, and it relies on the hosts firewall arrangements letting connections in on the port you chose (and the host having rsync installed in the first place). rsync requires a clean link with a shell that will allow it to start the remote copy of rsync, when run this way. Is there any chance of getting rsync sftp to work? The following link shows that it is possible to accomplish this task using fuse with sshfs - however it is extremely slow, and not fit for production use. Trying this on my system produced the following in out.dat:Īs I thought, the host is not allowing ssh logins. Mon cause is incorrectly configured shell startup scripts (such Then you will probably find that out.dat contains some text or Remote shell like this: ssh remotehost /bin/true > out.dat The way to diagnose this problem is to run your This message is usually caused by your startup scripts or

Here's the relevant section from the rsync man page: Rsync -av /source ssh version mismatch - is your However, trying to rsync to a host which allows only sftp logins, but not ssh logins, provides the following error:

Supersync sync push changes to remote