mldonkey-bugs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Mldonkey-bugs] [bugs #8812] files not commited when using compute_md4_d


From: anonymous
Subject: [Mldonkey-bugs] [bugs #8812] files not commited when using compute_md4_delay=0. (donkey/overnet)
Date: Wed, 05 May 2004 10:49:54 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040405 Firefox/0.8

This mail is an automated notification from the bugs tracker
 of the project: mldonkey, a multi-networks file-sharing client.




/**************************************************************************/
[bugs #8812] Full Item Snapshot:

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=8812>
Project: mldonkey, a multi-networks file-sharing client
Submitted by: 0
On: Wed 05/05/04 at 14:49

Category:  Core
Severity:  5 - Average
Item Group:  Program malfunction
Resolution:  None
Assigned to:  None
Status:  Open
Release:  2-5-20
Release:  
Platform Version:  Linux
Binaries Origin:  CVS / Self compiled
CPU type:  Intel x86


Summary:  files not commited when using compute_md4_delay=0. (donkey/overnet)

Original Submission:  mlnet is compiled with pthread support.
Since 2.5.18, files are not commited when using compute_md4_delay=0. .
When I say 'not commited' I mean the files stay in the list of download with 
percent=100%.
Using an external md4sum tool I can check the associated temp file has the 
correct md4sum.
Using compute_md4_delay=1. files get commited.
I think It should be easy to reproduce:
(i haven't tested with a non pthread mlnet)
 set compute_md4_delay 0.
 search -maxsize 2000 cue
 use the web interface to sort the results so that you can download files 
having the most complete sources.
 and tell me if you're able to reproduce it :)












For detailed info, follow this link:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=8812>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/







reply via email to

[Prev in Thread] Current Thread [Next in Thread]