mldonkey-bugs
[Top][All Lists]
Advanced

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

[Mldonkey-bugs] [bugs #9801] File is shared while downloading, but after


From: spiralvoice
Subject: [Mldonkey-bugs] [bugs #9801] File is shared while downloading, but after auto_commit the file is not shared at all (though finished)
Date: Tue, 10 Aug 2004 15:12:15 -0400
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.7) Gecko/20040616

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

/**************************************************************************/
[bugs #9801] Latest Modifications:

Changes by: 
                spiralvoice <address@hidden>
'Date: 
                Tue 08/10/2004 at 18:55 (Europe/Berlin)

------------------ Additional Follow-up Comments ----------------------------
Please check if this bug still is in current CVS version.
You should find a tarball of current CVS in files section of
this project: http://savannah.nongnu.org/download/mldonkey/






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

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=9801>
Project: mldonkey, a multi-networks file-sharing client
Submitted by: Roland Arendes
On: Wed 07/28/2004 at 14:00

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


Summary:  File is shared while downloading, but after auto_commit the file is 
not shared at all (though finished)

Original Submission:  I'm using 2.5.16t compiled with ocaml 3.08 (spiralvoice). 

I noticed the following behaviour: 

I have a mldonkey running with 0 files downloading and some files in my 
incoming-dir. 

I download a huge file, which is beeing actively shared while it is downloaded. 
After downloading (auto_commit!) the file is moved into the incoming-dir and is 
away. No sharing. The file is not listed in shared_files_new.ini, not listed in 
"links" or "upstats" and not published on any server. 

The command reshare, which should check this problem and hash newly detected 
files, does nothing. It just says "check done" without checking or noticing 
anything at all. 
Which means: If the core isn't restarted, I won't share the files I downloaded 
in this session. This behaviour is destructive. 
  
If I stop the core and restart it it logs "NEW SHARED FILE ...." and begans to 
hash it. After that the file is shared as usual. 

Now if I want to share a completely new file: 

The core is running. I copy the new file into my incoming dir, chmod 666. The 
core notices nothing, not even after using reshare. The same thing. even "share 
incoming/" does not work.  The not so funny issue is: The file is even ignored 
after restarting the core! No NEW SHARED FILE, .. nothing. I am not able to 
share a complete new file. 
It is not listed in links, upstats and isn't published at all. 

This bug seems to be very old. Please fix it, the 2.5.16 is a really good 
series of mldonkey and that bug is very network destructive and causes mldonkey 
to not share files it has downloaded. 

Why does not reshare do the same thing like the function that is called on 
startup (NEW SHARED FILE..) ?? 

Can someone with ocaml-knowlegde please have a look? 
Thanks 

Cheers 
chemical

Follow-up Comments
------------------


-------------------------------------------------------
Date: Tue 08/10/2004 at 18:55       By: spiralvoice
Please check if this bug still is in current CVS version.
You should find a tarball of current CVS in files section of
this project: http://savannah.nongnu.org/download/mldonkey/












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

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







reply via email to

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