Ian,
> Anybody got any ideas why i could rsync without problems using 2.4.6 a few
> weeks ago and not now?
As I have mentioned before these sorts of reports are impossible to
answer without basic information. The info needed is:
- versions of OS at both ends
- versions of ssh at both ends
- ve
Sorry guys for the previously stupid post. I fixxed my
problem by excluding Network Trash Folders that the
Macintoshes created on our server.
Sorry.
Tyler.
Tyler Hardison It is better to shut your mouth and be
a fool,
Systems Administrator
On Thu, Oct 19, 2000 at 02:23:31PM -0400, Neil Schellenberger wrote:
> > "ian" == ian stanley <[EMAIL PROTECTED]> writes:
>
> ian> Anybody got any ideas why i could rsync without problems
> ian> using 2.4.6 a few weeks ago and not now?
>
> Ian,
>
> Has the total "expected" transfer
It is time to recompile rsync with -g and wait for another hang.
eric
(gdb) attach 17407
Attaching to process 17407
(no debugging symbols found)...done.
0xff215d08 in _poll ()
(gdb) n
Single stepping until exit from function _poll,
which has no line number information.
0xff1ce6dc in select ()
(
Use lsof instead of pfiles if you have lsof available.
I have a version of strace for Solaris 2.6 that I fixed to grok socket
calls. It doesn't grok *64() calls, unfortunately, but I will someday
fix it to do so. It's not in any shape that cna be contributed back to
the strace project and it's r
More info/questions: (hung rsync is 17407)
# /usr/proc/bin/pstack 17407
17407: /usr/local/bin/rsync -rptgoD --partial --delete-after -vv
--delete -e
ff215d08 poll (ffbefad0, 0, 14)
ff1ce6d4 select (ffbefad0, ff2369f4, ff2369f4, ff2369f4, ff2369f4,
0) + 298
0001b568 msleep (14, ffbef
Eric,
Since the poll is nfds=0 and timeo=20 (i.e. almost certainly
msleep(20)) and since waitpid is looking for 17408, this actually
really has to be the call of wait_process() at main.c:532 where rsync
is (apparently) waiting for ssh to die.
The reason that timeout has no effect is that only i
> "Eric" == Eric Whiting <[EMAIL PROTECTED]> writes:
Eric> Forgot to say that I love rsync. :) I don't mean to sound
Eric> like a complainer or rsync-grump. I'm just trying to help
Eric> out a little bit. All these reports of problems are not
Eric> show-stoppers and only seem
> "ian" == ian stanley <[EMAIL PROTECTED]> writes:
ian> Anybody got any ideas why i could rsync without problems
ian> using 2.4.6 a few weeks ago and not now?
Ian,
Has the total "expected" transfer time increased over the past few
months? My impression is that most of the EOF/hang
I have been having a number of problems with rsync over the last few months
Originally we were using an early version of 2.x but after reading some of
your posts we upgraded to 2.4.6 which seemed to solve then problems - at
least in the short term.
That was until we did a release earlier this
10 matches
Mail list logo
