Hello guys, It looks as if I am having exactly the same problem as Jay described with sftp. In fact, it looks on my machine as if opie_sync successfully retrieves addressbook.xml to /tmp, but believes it has failed, so perhaps it is something simple to do with checking the exit code?
I tested on the command line and a successful copy appears successful to bash (see below). I haven't looked at the opie_sync code. Tom: many thanks for taking the time to reply to me. Together with one of the other notices (to reset the password to "rootme") I can now sync using ftp on port 4242. I hadn't realised there was an ftp server running there by default! The synchronization appears to work, although messages appear in the log like this: Sync. of 441 entries succeeded Failed to connect to remote: failed to flush todolist and similarly for "datebook" (frustratingly I can't cut and paste from the log window to show precise messages). - David. [EMAIL PROTECTED] da]$ if sftp -o Port=22 -o BatchMode=yes [EMAIL PROTECTED]:/root/postinst postinst; then echo yes; else echo no; fi Connecting to 192.168.220.2... Fetching /root/postinst to postinst yes Tom: many thanks for your helpful reply. On Tue, 2003-10-14 at 19:43, Eike M. Lang wrote: > Am Die, den 14.10.2003 schrieb Jay R. Gindin um 19:51: > > > (opie_sync.c[115] - 2003/10/14 17:47.38) sync_connect > > (opie_sync.c[126] - 2003/10/14 17:47.38) qcop_connect > > (opie_sync.c[151] - 2003/10/14 17:49.38) QCop connection failed > > > Now, if I turn off qcop: > > > (opie_sync.c[115] - 2003/10/14 17:50.54) sync_connect > > (opie_sync.c[126] - 2003/10/14 17:50.54) qcop_connect > > (opie_comms.c[213] - 2003/10/14 17:50.54) Attempting scp Connection. > > (opie_comms.c[490] - 2003/10/14 17:50.55) SFTP failed > > > This makes it look like it's attempting to do something with qcop, even > > when turned off??? > > Sorry, that's my bad. The debug statement for QCop is rather stupidly > placed outside the block that only gets executed when QCop is active. It > is as I suspected - sftp fails or appears to fail from multisync's point > of view for reasons that are not all obvious -- after all you did it > successfully on the command line. :-/ > > However, from the log entries it is obvious that ftp is not actually > being used (instead it is still sftp), the log messages are different > for FTP (just double-checked against the source). > > Tom, any ideas from you? I appear to be fresh out :-/ > > Regards, > Eike -- David Aspinall, email: [EMAIL PROTECTED] LFCS, School of Informatics, URL: http://homepages.inf.ed.ac.uk/da University of Edinburgh, Tel: +44 (0)131 650 5177 King's Buildings, Fax: +44 (0)131 667 7209 Edinburgh. EH9 3JZ U.K. Office: Room 2606, JCMB ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Multisync-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/multisync-users
