First - nice subject. On the rsync list, it's good to tell everybody that your question concerns rsync. I mean, we'd never guess that, and just that subject alone gives an indication of the nature of the problem, right?
Anyway, the rsync process you're invoking is not making contact with the rsync on domain.ltd. Either you're not successfully establishing a shell connection, or the one you establish isn't finding the rsync binary on the remote. First, "rsync -vvv [EMAIL PROTECTED]:". That'll give you something like this if your transport is rsh. +++++++++++++++++++++++++++++++++++++++++++++++++++ [EMAIL PROTECTED] /home/cnwt99>rsync -vvv [EMAIL PROTECTED]: opening connection using rsh -l ync domain.ltd rsync --server --sender -vvvr . Failed to dup/close : Socket operation on non-socket rsync error: error in IPC code (code 14) at /home/lapo/packaging/tmp/rsync-2.6.0/pipe.c(68) _exit_cleanup(code=14, file=/home/lapo/packaging/tmp/rsync-2.6.0/pipe.c, line=68): about to call exit(14) rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Connection reset by peer rsync error: error in rsync protocol data stream (code 12) at /home/lapo/packaging/tmp/rsync-2.6.0/io.c(666) _exit_cleanup(code=12, file=/home/lapo/packaging/tmp/rsync-2.6.0/io.c, line=666): about to call exit(12) [EMAIL PROTECTED] /home/cnwt99> ++++++++++++++++++++++++++++++++++++++++++++++++++++++ Or like this if your transport is ssh. ++++++++++++++++++++++++++++++++++++++++++++++++++++++ [EMAIL PROTECTED] /home/cnwt99>rsync -vvv [EMAIL PROTECTED]: opening connection using ssh -l ync domain.ltd rsync --server --sender -vvvr . Failed to dup/close : Socket operation on non-socket rsync error: error in IPC code (code 14) at /home/lapo/packaging/tmp/rsync-2.6.0/pipe.c(68) _exit_cleanup(code=14, file=/home/lapo/packaging/tmp/rsync-2.6.0/pipe.c, line=68): about to call exit(14) rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Connection reset by peer rsync error: error in rsync protocol data stream (code 12) at /home/lapo/packaging/tmp/rsync-2.6.0/io.c(666) _exit_cleanup(code=12, file=/home/lapo/packaging/tmp/rsync-2.6.0/io.c, line=666): about to call exit(12) [EMAIL PROTECTED] /home/cnwt99> ++++++++++++++++++++++++++++++++++++++++++++++++++++++ That "opening connection" line is the key. It'll be like the above, or Try a connection using the shell command up to the "rsync". If that works, try that same command, ending in "which rsync". If it's not finding the remote rsync, find it, and add it with "--rsync-path=" to your rsync commandline, or symlink it in somewhere on the stripped-down remote shell $PATH. Good luck. Tim Conway Unix System Administration Contractor - IBM Global Services [EMAIL PROTECTED] alexus <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 03/09/2004 09:54 PM To [EMAIL PROTECTED] cc Subject rsync d# rsync -vcrlpogtz . [EMAIL PROTECTED]:/export/home/rsync/ [EMAIL PROTECTED]'s password: sh: rsync: rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) d# Can someone tell me what am I doing wrong? Thanks - -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
