Ken Senior wrote:
Pushing from Windows to Linux works fine. It's the pulling from Windows
into Linux (that is, initiating on Linux) which does not.
On the gdb front, I found that whenever I launched the gdb on the
Windows box, the process froze immediately instead of the usual place.
That is,
Pushing from Windows to Linux works fine. It's the pulling from Windows
into Linux (that is, initiating on Linux) which does not.
On the gdb front, I found that whenever I launched the gdb on the
Windows box, the process froze immediately instead of the usual place.
That is, the gdb process seem
> My chief purpose for all of this is to allow automatic backups onto a
> Linux file server from various systems (initiating on the Linux box),
> including Windows PCs.
Interesting, so your implementing a pull vs. a push. That is the Linux
box is logging into the Windows and pulling files back.
On Sun, 8 Jan 2006, Ken Senior wrote:
> I am at home today and cannot perform all of these, but on the Linux ->
> Windows, I was able to issue the rsync on [LOCAL/Linux] and then attach
> to the rsync process on [REMOTE/Windows] using gdb with the resulting
> backtrace output:
>
> $ gdb rsync 3032
I am at home today and cannot perform all of these, but on the Linux ->
Windows, I was able to issue the rsync on [LOCAL/Linux] and then attach
to the rsync process on [REMOTE/Windows] using gdb with the resulting
backtrace output:
$ gdb rsync 3032
GNU gdb 6.3.50_2004-12-28-cvs (cygwin-special)
Co
> > 3. To answer your earlier question, I installed cygwin and added
> > the rsync and openssh which were part of the distribution but
> > were not installed by default. I did not compile my own.
>
> Whis is like the usual package list I do use most commonly. I
> never managed to reproduc
Brett Serkez serkez.net> writes:
> As far as using gdb, rather than using the full rsync command line, use
> the command 'gdb rsync' to start rsync in the debugger. Then enter the
> command 'run balance-of-rsync-command-line' and it should run normally.
> Once it hangs, use control-c to break to
Ken Senior gmail.com> writes:
> 2. The process seems to stop at one or two of the same files each time:
>run1 : hung at file Abytes transferred: 2,392,064
> run2 : hung at file Bbytes transferred: 2,408,448
Uhm, and what about the file set: how big is it? How many files?
I
Ken Senior gmail.com> writes:
> 3. To answer your earlier question, I installed cygwin and added the
> rsync and openssh which were part of the distribution but were not
> installed by default. I did not compile my own.
Whis is like the usual package list I do use most commonly. I never manage
<...snip...>
> Does this tell anyone anything? If not, I could traverse the learning
> curve on getting gdb information from the process.
As an additional thought on why rsync may be hanging on a write to
stdout, presuming the cause is a deadlock. What is the size of the file
it is hanging on?
<...snip...>
> Does this tell anyone anything? If not, I could traverse the learning
> curve on getting gdb information from the process.
As a point of information, when rsync is run, as in this case using ssh,
it is using ssh to start a remote rsync on the server. These two rsyncs
are able to c
I apologize if you get this twice, but the cygwin server rejected this
post when I sent it from my gmail web account complaining of invalid MIME.
So, per Brett's suggestion I downloaded & compiled rsync on my cygwin
installation, call it [REMOTE/Windows], in order to diagnose the problem
and inde
I'm not sure, other than what you've already pointed out, the number of
bytes being close to a magic number, almost like a counter or index is
overflowing.
I'd be inclined to build my own rsync for debugging, start it under gdb,
continue and when it hangs, use control-c and trace to see where it
Let me say again, THANKS for helping!
Well, the screen has stayed frozen for some 10 minutes. Some observations:
1. Killing the rsync process (CTRL-C) on [LOCAL/Linux] does not kill
the process on [REMOTE/Windows]. I have to kill the process manually on
[REMOTE].
2. The process seems to stop
Ken,
The rsync protocol actually does check-suming of blocks to efficiently
detect and transfer files. While it may look like it is hung, it may
actually be just transfering check sums on each file. When I perform
long transfers it looks hung from time to time, but my use of the extra
v switches
Thanks Brett for the quick reply. The multiple -v is a handy thing to
remember.
In fact this is not my problem though. It looks like the listing of
files just hangs midstream. Some local directories are created and
sometimes a few files make it too, but it just hangs. For example:
.
.
Ken,
I run rsync both Windows and Linux to Linux, Linux always being the
'server'. In my case I found the hang to be up front, before secure
shell even attempted to access the network and also in my case changing
from a local socket to a local pipe resolved the issue:
http://cygwin.com/ml/cygwin
17 matches
Mail list logo
