[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Mldonkey-bugs] [Bug #1448] commit problem
From: |
nobody |
Subject: |
[Mldonkey-bugs] [Bug #1448] commit problem |
Date: |
Wed, 23 Oct 2002 02:53:17 -0400 |
=================== BUG #1448: LATEST MODIFICATIONS ==================
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=1448&group_id=1409
Changes by: Simon Turvey <address@hidden>
Date: 2002-Oct-23 06:53 (GMT)
------------------ Additional Follow-up Comments ----------------------------
This is a common problem arising from launching mldonkey into the background
without redirecting stdout/stderr.
Launch with "mldonkey &> /dev/null" or name a file to capture the output.
=================== BUG #1448: FULL BUG SNAPSHOT ===================
Submitted by: None Project: mldonkey, a free e-Donkey
client
Submitted on: 2002-Oct-18 20:08
Category: Core Severity: 5 - Major
Bug Group: None Resolution: None
Assigned to: None Status: Open
Release: 2.00 Release:
Platform Version: Linux i386-i686 Binaries Origin: None
Summary: commit problem
Original Submission: I downloaded the latest precompiled mldonkey 2.0, and I
find the following problem,
after some files finish downloading, if I use commit to commit the file,
the terminal will show me Input/Output Error.
The file then disappeared, If I use scan_temp, the file is there. then I use
recover_temp, the percentage will become 0, I have to start over again. This
problem have happened quite often.
I even download the latest cvs source code and recompile by myself, still
exist. Do you have any suggestion?
Follow-up Comments
*******************
-------------------------------------------------------
Date: 2002-Oct-23 06:53 By: turveysp
This is a common problem arising from launching mldonkey into the background
without redirecting stdout/stderr.
Launch with "mldonkey &> /dev/null" or name a file to capture the output.
CC list is empty
No files currently attached
For detailed info, follow this link:
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=1448&group_id=1409