Re: [92] [Libbt-devel] Re: Features request

[Kevin S. <ke...@an...>]

Elliott Mitchell wrote:

>>From: Diego Casorran <di...@us...>
>>On 20-05-2005 (08:34:57), you wrote:
>>
>>    
>>
>>>you can always make a script in which you run btget in a while loop, so,
>>>if it  dies, it restarts...
>>>
>>>      
>>>
>>yeah, but my intention was to avoid the current downloaded torrent being 
>>re-seeded for ok pieces every loop.
>>    
>>
>
>All BT clients do this.
>
>  
>
>>>an assertion is there to tell us that there is a bug in programming,
>>>it's not  it's job to restart btget.
>>>
>>>Since I'm not involved in the release, i cannot answer the rest of your 
>>>questions and i cannot direct your concerns...
>>>
>>>btw: i never heard about trackers that request user/passwd, can you send
>>>us  one?
>>>
>>>      
>>>
>>its attached, seems that all torrents from www.pctorrent.com needs a user&pass
>>to connect to his tracker, however not a great problem, later or sonner they
>>will be available from somewhere else..
>>    
>>
>
>This might be a case of it gives you a modified URL which you use to
>connect to the tracker. Along the lines of
><trackerurl>&&user=<foo>&&pass=<bar> and you're supposed to connect to
>a central webserver to get those two values. If so, this isn't something
>for the BT client, just how you get the .torrent file.
>
>BTW one of the anti-viral things out there ate the file (not that I'm
>worried about Linux getting hit, but something did eat it).
>
>  
>
>>>what is your OS and libbt version
>>>
>>>      
>>>
>>AmigaOS.. and 1.04
>>    
>>
>
>IT STILL LIVES!!! Sigh.  :'-(   I wonder if v4 is ever going to happen.
>
>  
>
>>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.
>
>
>  
>
127.*.*.*/8 are all loopback devices.  Your tracker shouldn't be 
returning anything in that range, but I've fixed some of the error 
handling when a connect fails immediately, so the synch error should go 
away.  Test the latest release branch and let me know if it works for you.