On 10/18/06, Morita Sho [EMAIL PROTECTED] wrote:
I can't determine that this comment should be send to bug#387658 that is already
closed. Let me know if you think this comment should be send as new bugreport.
I don't think it's a new bug, as it hasn't yet caused any problems. If
it does cause
Cameron Dale wrote:
I don't think it matters, as the new function start() is called from
inside the __init__() functions try statement, and so any unhandled
exceptions in the start() function will be passed back to the
__init__() functions except statement. That is my understanding of how
Hi!
I can't determine that this comment should be send to bug#387658 that is already
closed. Let me know if you think this comment should be send as new bugreport.
I have installed bittornado 0.3.15-3, and confirmed that bug#387658 is fixed.
I have checked the source code of BitTornado to see
tags 387658 +pending
thanks
On 9/19/06, Morita Sho [EMAIL PROTECTED] wrote:
I have said that btlaunchmany does not send event=stopped to the tracker on
exit.
event=stopped means I'm exiting.
That is, btlaunchmany exited without telling I'm exiting to the tracker.
So that the client is remain
Sorry, my first post have not enough explanation.
So I will supplement about that.
I have said that btlaunchmany does not send event=stopped to the tracker on
exit.
event=stopped means I'm exiting.
That is, btlaunchmany exited without telling I'm exiting to the tracker.
So that the client is
Package: bittornado
Version: 0.3.15-2
Severity: normal
btdownload and btlaunchmany send event=started to tracker on startup.
And when quitting, btdownload send event=stopped to tracker,
but btlaunchmany does not send event=stopped to tracker.
I have found this problem using Wireshark, network
6 matches
Mail list logo
