bugmldonkey, a multi-networks file-sharing client - Bugs: bug #1566, cannot "kill" core on...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #1566: cannot "kill" core on MDK 8.1

Submitted by:  None
Submitted on:  Thu 31 Oct 2002 12:40:31 PM UTC  
 
Category: CoreSeverity: 3 - Normal
Item Group: NoneStatus: Remind
Assigned to: NoneOpen/Closed: Closed
Release: Release: 2.00
Operating System: LinuxBinaries Origin: Binary from Savannah
CPU type: None

(Jump to the original submission Jump to the original submission)

Tue 02 Dec 2003 06:21:19 PM UTC, comment #6:

This patch report is very old. If the bug still exists in current
versions please post a new bug report - spiralvoice

spiralvoice <spiralvoice>
Project Administrator
Tue 04 Mar 2003 07:45:44 AM UTC, comment #5:

Indeed, mldonkey should start as a daemon (with a -no-daemon when we want output on the console), and we should have a 'log' command to redirect the output when needed. Put on the TODO list.

mldonkey admin <mldonkey>
Project Administrator
Tue 26 Nov 2002 11:12:20 AM UTC, comment #4:

do NEVER EVER use kill -9 on mldonkey. Try this script instead:

#!/bin/sh

case "$1" in
start)
if [ -n "`/sbin/pidof mldonkey`" ]; then
echo "mlDonkey already running.."
else
cd /home/donkey/mldonkey/build
nice -10 ./mldonkey >/dev/null 2>errlog &
echo "mlDonkey started.."
fi
;;

stop)
if [ -n "`/sbin/pidof mldonkey`" ]; then
kill -INT `/sbin/pidof mldonkey`
echo -n "mlDonkey contacted .. "
while [ -n "`/sbin/pidof mldonkey`" ]; do
sleep 2
echo -n "."
done
echo "stopped."
else
echo
echo "No mlDonkey found to kill."
fi
;;

restart)
$0 stop && $0 start
;;

status)
echo -n "Checking mldonkey: "
checkproc /home/donkey/mldonkey/build/mldonkey && echo OK || echo No process
;;

*)
echo "Usage: $0 {start|stop|restart|status}"
exit 1
;;

esac

Anonymous
Tue 26 Nov 2002 01:04:11 AM UTC, comment #3:

Well, kill -9 works, but I'm afraid of choosing this as my shutdown method for ml because I don't know what happens with running downloads and/or not written data. Also there are some *.tmp files left from time to time when -9'ing which leads to an error when ml is started the next time.
I'll try to redirect the Output, thx for the hint.

Anonymous
Fri 22 Nov 2002 02:48:33 PM UTC, comment #2:

I guess mldonkey shutdown in stopped because of a Exception("Sys I/O error") (sp?) because it can't write some message to STDERR.
Do not close the terminal it's running from, or redirect STDOUT and STDERR to a file (or /dev/null):

nohup ./mldonkey >/dev/null 2>/dev/null &

Anonymous
Thu 07 Nov 2002 08:16:14 AM UTC, comment #1:

I have exactly the same problem under FreeBSD 4.7 release
Berte

Anonymous
Thu 31 Oct 2002 12:40:31 PM UTC, original submission:

Hello,
from time to time, my freshly installed v2.00 of mlDonkey cannot be "kill"ed via telnet. Not even a "killall mldonkey" issued via commandline works. I have to reboot in order to shut down mlDonkey.

Anonymous

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 2 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Tue 02 Dec 2003 06:21:19 PM UTCspiralvoiceOpen/ClosedOpen=>Closed
Tue 04 Mar 2003 07:45:44 AM UTCmldonkeyStatusNone=>(Error - Not Found)

Back to the top


Powered by Savane 3.1-cleanup1