Hello
I'm having a heck of a time rsync'ing (is that the proper conjugation?
:)) between two Cygwin machines. I have three directory trees that are
"exposed" via rsynch. Two of the three have a very shallow structure,
and they work fine. The third, however, has a fairly deep structure and
many more files than the other two, and rsync'ing this directory causes
a hang on the client side.
Firing up gdb, I get:
(gdb) list
486 phase++;
487 csum_length = SUM_LENGTH;
488 ignore_times=1;
489
490 if (verbose > 2)
491 rprintf(FINFO,"generate_files
phase=%d\n",phase);
492
493 write_int(f,-1);
494
495 if (remote_version >= 13) {
(gdb) n
generate_files phase=1
493 write_int(f,-1);
(gdb) n
495 if (remote_version >= 13) {
(gdb) print remote_version
$1 = 26
(gdb) n
498 for (i=read_int(f_recv); i != -1; i=read_int(f_recv)) {
(gdb) n
rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)
rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)
Program exited with code 024.
(gdb)
So it hangs in read_int ... probably because the server doesn't send
anything.
Both client and server are running:
rsync version 2.5.2 protocol version 26
Copyright (C) 1996-2002 by Andrew Tridgell and others
<http://rsync.samba.org/>
Capabilities: 32-bit files, socketpairs, hard links, symlinks, batchfiles, no IP
v6,
32-bit system inums, 64-bit internal inums
Both client and server are using Cygwin 1.3.10-1, but this has happened
on other versions as well. I'm using "-e ssh" and my ssh version
on
both client and server is 3.0.2p1-5 (the latest available from Cygwin
mirrors).
What other information can I provide that might help this get resolved?
Also, what's the recommended way of shutting off the signal handler (so
that I can ^C in gdb and not exit the program).
CC: me on replies please.
--
Ryan T. Sammartino
http://members.shaw.ca/ryants/
Is there life before breakfast?
