rsync troubles

[Peter Barker]

On Tue, 25 Sep 2001, Bob Edwards wrote:

> Contrary to what Steven wrote, rsync does not do a checksum of every
> file, only of those files who's size and modification times are
> different at each end.

... unless you pass it the appropriate option.

Actually, rsync is very good at finding problems with tcp/ip stacks. Is it
possible that it is finding problems in the Solaris stack?

What does strace show you on either end? ltrace? rsync -vvvvvvvvvvvvvvv
(errr... you get the idea :-) tcpdump? top? fprintf(3) and gcc? Lots of
debugging options :-)

If you don't already have a copy of the filing system on the other end, I
often use netcat and tar....

On sender: tar c /etc | nc destination 7863
On receiver (in appropriate directory...): nc -l -p 7863 -w 10 | tar x

Adding the z option is entirely dependant on the link.

> Bob Edwards.

Yours,
-- 
Peter Barker                          |   N    _--_|\ /---- Barham, Vic 
Programmer,Sysadmin,Geek              | W + E /     /\                
pbarker at barker.dropbear.id.au         |   S   \_,--?_*<-- Canberra      
You need a bigger hammer.             |             v    [35S, 149E]   
"When used legally and in its intended fashion, the Acrobat eBook Reader
 secures eBooks purchased by locking the eBook to the hardware from which
 it was purchased." -- Adobe press release