Hello, from a server where neither a rsync daemon nor ssh is running I'm trying to backup the whole data with ftp. So my idea was to call rsync like this: rsync -v -a 'ftp://1.2.3.4/' my_folder But this gives me: ftp: unknown host ftp: unknown host ftp: Unknown host rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) Doesn't rsync handle ftp://? Regards Marten
On Fri, 2005-12-02 18:25:37 +0100, Marten Lehmann <lehmann@cnm.de> wrote:> from a server where neither a rsync daemon nor ssh is running I'm trying > to backup the whole data with ftp. So my idea was to call rsync like this: > > rsync -v -a 'ftp://1.2.3.4/' my_folderDo you really expect a program implementing the RSYNC protocol to talk to a machine which has some software running speaking the FTP protocol? This won't fly... You need to use a FTP client is a FTP server is installed. MfG, JBG -- Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _ "Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O f?r einen Freien Staat voll Freier B?rger" | im Internet! | im Irak! O O O ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA)); -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.samba.org/archive/rsync/attachments/20051202/82578684/attachment.bin
I am sorry, the rsync algorithm needs to execute rsync on the server. Since ftp does not allow executing remote programs (as ssh does), even if there exists a rsync executable installed in the server and you have permission to execute it, using ftp you cannot execute it. So your command won't work and it will never be because it is impossible to implement it by the very differences of what rsync does (executing a remote rsync program) and how ftp works (just download files). I hope my answer was clear to you. Cheers, Manuel. Marten Lehmann wrote:> Hello, > > from a server where neither a rsync daemon nor ssh is running I'm trying > to backup the whole data with ftp. So my idea was to call rsync like this: > > rsync -v -a 'ftp://1.2.3.4/' my_folder > > But this gives me: > > ftp: unknown host > ftp: unknown host > ftp: Unknown host > rsync: connection unexpectedly closed (0 bytes read so far) > rsync error: error in rsync protocol data stream (code 12) at io.c(165) > > Doesn't rsync handle ftp://? > > Regards > Marten______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, m?s seguridad http://correo.yahoo.es
Here are some suggestions for ftp clients: ftp wget ncftp all of the above can be scripted and automated to download or upload specific files. Regards, Brad. On 2 Dec 2005, at 17:25, Marten Lehmann wrote:> Hello, > > from a server where neither a rsync daemon nor ssh is running I'm > trying to backup the whole data with ftp. So my idea was to call > rsync like this: > > rsync -v -a 'ftp://1.2.3.4/' my_folder > > But this gives me: > > ftp: unknown host > ftp: unknown host > ftp: Unknown host > rsync: connection unexpectedly closed (0 bytes read so far) > rsync error: error in rsync protocol data stream (code 12) at io.c > (165) > > Doesn't rsync handle ftp://? > > Regards > Marten > -- > To unsubscribe or change options: https://lists.samba.org/mailman/ > listinfo/rsync > Before posting, read: http://www.catb.org/~esr/faqs/smart- > questions.html-- Brad Rigden Senior Systems Administrator @ Fotango Ltd. Mobile: +44 (0) 79 6716 2117
hashproduct@verizon.net wrote:> >On Fri, 2005-12-02 at 17:41 +0000, Manuel >L?pez-Ib??ez wrote: >> I am sorry, the rsync algorithm needs to execute >rsync on the server. >> Since ftp does not allow executing remote >programs (as ssh does), even >> if there exists a rsync executable installed in >the server and you have >> permission to execute it, using ftp you cannot >execute it. So your >> command won't work and it will never be because >it is impossible to >> implement it by the very differences of what >rsync does (executing a >> remote rsync program) and how ftp works (just >download files). > >In my opinion, that's a perfect explanation. > >However, Marten is probably far from the only >person who would love to >use rsync over an FTP connection. Its flexibility >has to surpass that >of just about every tool that does support FTP.However, due to stuff like limited firewalls on either side, DOS/UNIX/MAC text files, FTP does not always support FTP. I doubt that rsync can/should fill in the missing gaps. Rsync's dominant advantage is when there is a lot in common between the current source and a stale almost copy on the target. This requires rsync access to the filesystems on BOTH sides of the transfer. Copying by ftp and then rsyncing cannot gain much if anything over just ftping. Switches, control, etc seems much more elaborate and competent, probably because the differences matter much more when stuff is remote and longwinded and subject to somebody pulling the plug mid-copy. I will often use rsync for a local-local copy when something else would actually be faster and maybe better because I know rsync switches which do something I can live with and I sometimes get nasty surprises because I use the wrong switches with the something else. Unlikely, but IF, GIANT SIZED IF, the rsync switches are consonant with playing with ftp (doing similar to wget, but also with an wput counterpart), it would be quite convenient in a lot of cases. Unfortunately, if I had to bet, I'd bet for something lurking that makes it a very bad idea. A number of ftp problems show up as rsync errors. How to interpret those errors. I think they lose in the translation.