mldonkey-bugs
[Top][All Lists]
Advanced

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

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


From: nobody
Subject: [Mldonkey-bugs] [Bug #1566] cannot "kill" core on MDK 8.1
Date: Tue, 04 Mar 2003 02:45:44 -0500

=================== BUG #1566: LATEST MODIFICATIONS ==================
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=1566&group_id=1409

Changes by: mldonkey admin <address@hidden>
Date: Tue 03/04/03 at 07:45 (GMT)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | None                      | Remind


------------------ Additional Follow-up Comments ----------------------------
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.




=================== BUG #1566: FULL BUG SNAPSHOT ===================


Submitted by: None                    Project: mldonkey, a free e-Donkey client
Submitted on: Thu 10/31/02 at 12:40
Category:  Core                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  Remind                   
Assigned to:  None                    Status:  Open                         
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 03/04/03 at 07: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/02 at 11: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/02 at 01: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/02 at 14: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/02 at 12:32         By: cascade
tried
kill -9 PIDOFMLDONKEY 
?

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


CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=1566&group_id=1409




reply via email to

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