> -----Original Message-----
> From: balloon-admin@balloonboard.org 
> [mailto:balloon-admin@balloonboard.org] On Behalf Of Wookey
> Sent: 30 December 2004 22:15
> To: balloon@balloonboard.org
> Subject: [Balloon] Re: 0.7 release
> 
> 
> +++ Glen VanMilligan [04-12-30 14:52 -0800]:
> > On Wednesday 22 December 2004 09:16, Wookey wrote:
> > > #update important stuff from husaberg
> > >
> > > BASEFILE=/home/aleph1/armlinux/boards/balloon/husaberg
> > > SOURCE=rsync://husaberg.toby-churchill.com/balloon
> > > for DIR in "releases" "linux-2.4.25-vrs2-tcl1" 
> "linux-2.6.8.1-tcl1" 
> > > do
> > >   rsync -avzx --delete-after $SOURCE/$DIR $BASEFILE/$DIR done
> > Wookey,
> > I get the following error when I try to access the source:
> > 
> > linux:/home # /usr/bin/rsync -avzx --delete-after
> > 
> rsync://husaberg.toby-churchill.com/balloon/linux-2.4.25-vrs2-
> tcl1 
> /home/aleph1/armlinux/boards/balloon/husaberg/linux-2.4.25-vrs2-tcl1
> > rsync: failed to connect to husaberg.toby-churchill.com: 
> Connection refused
> > rsync error: error in socket IO (code 10) at clientserver.c(88)
> > linux:/home #
> 
> Hmm, well you ought to change BASEFILE to suit your setup (I 
> don't suppose you have a directrory called 
> home/aleph1/armlinux/boards/balloon/husaberg in which you 
> want a copy of the husaberg stuff).
> 
> Also that rsync line I posted was wrong (it gave an extra 
> directory you don't need) it should be: rsync -avzx 
> --delete-after $SOURCE/$DIR $BASEFILE
> 
> However none of that accounts for the rsync IO error you are 
> getting. I just ran the script from here this moment and it 
> works OK, so either you have a problem with rsync and your 
> firewall or the husberg server is ignoring you. UNfortunately 
> rsync's errors are deeply unhelpful so it's hard to know 
> exactly what's going wrong.
> 
> Jenny - what do the husaberg logs say? Any clues?
> 
> 
> Wookey
Hi,
Sort of. If I try
"rsync -avzx rsync://husaberg.toby-churchill.com/balloon/linux-2.4.25-vrs2-tcl1 ." 
I get the expected directory rsyncing across.
Log file for this transfer and the transfer on 30/12/04 late in the day (which I assume was you, Wookey) both report thusly:
2004/12/30 23:00:27 [24641] rsync on balloon/releases from UNKNOWN (81.20.11.33)
2005/01/04 11:15:20 [22457] rsync on balloon/linux-2.4.25-vrs2-tcl1 from UNKNOWN (192.168.10.111)
Whereas the log for the transfer requested earlier on the 30/12/04 (which I assume was Glen) reports:
2004/12/30 15:33:55 [23110] rsync on pub/. from UNKNOWN (81.20.7.6)
2004/12/30 15:34:05 [23110] rsync: writefd_unbuffered failed to write 4096 bytes: phase "send_file_entry": Connection reset by peer
2004/12/30 15:34:05 [23110] rsync error: error in rsync protocol data stream (code 12) at io.c(839)

 The difference is in the requested directory, which I don't understand, as it looks from the script Glen is using that he is requesting the same transfer as Wookey.
Glen, let me know if you are still having problems and I'll delve further.
Jenny

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________