mldonkey-bugs
[Top][All Lists]
Advanced

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

[Mldonkey-bugs] [bugs #1566] cannot "kill" core on MDK 8.1


From: spiralvoice
Subject: [Mldonkey-bugs] [bugs #1566] cannot "kill" core on MDK 8.1
Date: Tue, 02 Dec 2003 13:21:19 -0500
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.5) Gecko/20031007

This mail is an automated notification from the bugs tracker
 of the project: mldonkey, a free e-Donkey client.

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

Changes by: 
                spiralvoice <address@hidden>
'Date: 
                Tue 12/02/2003 at 19:21 (Europe/Berlin)

            What     | Removed                   | Added
---------------------------------------------------------------------------
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
This patch report is very old. If the bug still exists in current

versions please post a new bug report - spiralvoice






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

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=1566>
Project: mldonkey, a free e-Donkey client
Submitted by: 0
On: Thu 10/31/2002 at 13:40

Category:  Core
Severity:  5 - Average
Item Group:  None
Resolution:  Remind
Assigned to:  None
Status:  Closed
Release:  2.00
Release:  
Platform Version:  Linux i386-i686
Binaries Origin:  Downloaded from Savannah


Summary:  cannot "kill" core on MDK 8.1

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.

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


-------------------------------------------------------
Date: Tue 12/02/2003 at 19:21       By: spiralvoice
This patch report is very old. If the bug still exists in current

versions please post a new bug report - spiralvoice

-------------------------------------------------------
Date: Tue 03/04/2003 at 08:45       By: mldonkey
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.



-------------------------------------------------------
Date: Tue 11/26/2002 at 12:12       By: None
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



-------------------------------------------------------
Date: Tue 11/26/2002 at 02:04       By: None
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.

-------------------------------------------------------
Date: Fri 11/22/2002 at 15:48       By: None
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 &



-------------------------------------------------------
Date: Thu 11/07/2002 at 13:32       By: cascade
tried

kill -9 PIDOFMLDONKEY 

?

-------------------------------------------------------
Date: Thu 11/07/2002 at 09:16       By: None
I have exactly the same problem under FreeBSD 4.7 release

Berte












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

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





reply via email to

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