Re: rsync -vae ssh user@host1:/tmp/dir user@host2:/tmp/
On 10/24, jw schultz wrote: No. Use ssh to set up port forwarding. If you know not how, use the ssh resources. I can't because of firewalls. workstation can connect to port 22 on both host1 and host2. host1 cannot connect to any ports on either workstation or host2. host2 cannot connect to any ports on either workstation or host1. So if I understand correctly, port forwarding cannot resolve this problem, and the only solutions are to either implement the syntax in the subject of this email in rsync, or download everything from host1 to workstation temporarily, and then upload it all to host2 ? -- I would believe only in a God that knows how to Dance. - Nietzsche http://www.ChaosReigns.com -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync rcp
On 30 Oct 2003, [EMAIL PROTECTED] wrote: I was hoping that since you guys are the authors to rsync that you could answer a simple question for me. I'm trying to transfer files via the rsh/rexec protocol by remotely executing a cat command, i.e. cat foo.txt and then sending data through the socket to the stdin of the remote process. This all works fine, except for the fact that I have to close the socket to force and end of file. My question is, does rcp/rsync close a socket when it sends files to signify and end of file? If not, how does it send multiple files without closing the socket? It uses a binary protocol to delimit files and describe metadata such as their name and ownership. As you say you cannot use the end-of-file mark more than once. It is conceptually similar to a tar file. So if you wanted to send multiple files with just rsh, you could do tar c mydir | ssh somehost tar x [EMAIL PROTECTED] is a better forum for questions. -- Martin -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync -vae ssh user@host1:/tmp/dir user@host2:/tmp/
On Thu, Oct 30, 2003 at 02:17:51PM -0500, [EMAIL PROTECTED] wrote: On 10/24, jw schultz wrote: No. Use ssh to set up port forwarding. If you know not how, use the ssh resources. I can't because of firewalls. workstation can connect to port 22 on both host1 and host2. host1 cannot connect to any ports on either workstation or host2. host2 cannot connect to any ports on either workstation or host1. So if I understand correctly, port forwarding cannot resolve this problem, and the only solutions are to either implement the syntax in the subject of this email in rsync, or download everything from host1 to workstation temporarily, and then upload it all to host2 ? This is really an ssh issue but in breif. workstation$ ssh -R 12304:host2:22 host1 host1$ rsync -e ssh -p 12304 -a localhost:$src $dest This is an approximation only. The quotes are critical and may need a little tuning. You will need to do some work on host identification to get it to work. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
