Re: [Libbt-devel] Re: Features request

[Alien <ali...@us...>]

Op woensdag 25 mei 2005 07:59, schreef Diego Casorran:
>  Hello Elliott
>
> On 21-05-2005 (21:20:12), you wrote:
> > All BT clients do this.
>
> thats ok, ofcourse, what I mean (and afaik) on the program run all pieces
> are hashed (even if lseek() must expand the file), those which match are
> saved/remembered on memory, if there is some new piece before btget dies
> (in case of) they are stored on memory as well, when btget dies I wanted =
to
> just restart it without exit since all ok pieces are already stored on
> memory, and shouldn't be really needed to exit if you really do not want =
to
> exit (with a option, for example..), atleast when the mentioned assertion
> fails, I think.

I have worked out a solution for this on the CVS version, files aren't=20
increased in size by lseek anymore when checking them at the start.

> >> AmigaOS.. and 1.04
> >
> > IT STILL LIVES!!! Sigh.  :'-(   I wonder if v4 is ever going to happen.
>
> yeah, ofcourse.. :-)
>
> what? you wonder if AmigaOS v4.0 is going to happen? then I have great ne=
ws
> to you.. it is a reallity! it is currently/still being developed and
> already available and distributed with the new Amiga models (PowerPC
> G3/G4), dont hesitate to let me know if you need more info/specs/urls :)
>
> btw, that ":'-(" smiley means you melancolic? ...or?
>
> >> About the 'no route to host' problem, it is trying to connect to
> >> 127.1.1.1, whats this?... some other kind of local loopback address?
> >> never see it myself here, and how to work with it? I need to set it up
> >> on my computer or it is supposed to point the tracker/some badly
> >> configured peer?...
> >
> > You have a wacky tracker? Or wacky torrent? 127.1.1.1 should never be
> > seen anywhere. I've got no idea how it could possibly be generated
> > inside libbt. If that is somehow appearing, there might be something
> > scribbling on memory, otherwise the fault is *definitely* in some other
> > piece of software. At which point perhaps we document that said piece of
> > software is badly broken, but it is likely to induce bugs of our own to
> > handle.
>
> well, I dunno whats up here.. but for now I got that problem only fetching
> the attached torrent (however until todays Ive downloaded 4-5 torrents
> only), try and see it for yourself if you want, may you can discover whats
> wrong.

maybe someone on the tracker itself is down/up-loading and he gave the wron=
g=20
IP, or someone is using totally different routing in his LAN... the=20
specifications should tell us that 127.0.0.1/8 is routed to itself, and !no=
t!=20
127.0.0.1/24 or something...

i guess we'll have to put in an additional check to see if it's a valid IP.=
=2E.

AL13N