Deluge
It doesn't matter. `ps x` should provide all the information you need. Adding the 'a' displays all processes, not just those belonging to the current user, so unless you're running deluge as someone else, you're just typing an extra character. Adding the 'u' just adds a bunch of columns you don't need for finding the PID (e.g., user, cpu/memory stats, the date the process was started, etc.).lifestyle wrote:So, is it ps x | grep deluge or ps aux | grep deluge?
Hehe. The second process is you grepping for deluge in the output of `ps aux`. It ends after it finishes its task, so it isn't around for you to kill. Only the first one needs to be killed.lifestyle wrote:I do not quite understand how to kill a pid... take a look at what I have tried:
$ deluge
create proxy object
create iface
send to iface
$ ps aux | grep deluge
pc 5839 2.1 4.7 167308 48760 ? Sl Nov25 8:16 /usr/bin/python2.5 /usr/bin/deluge
pc 8867 0.0 0.0 2976 748 pts/0 R+ 04:56 0:00 grep deluge
$ kill 5839
$ kill 8867
bash: kill: (8867) - No such process
$
Do I kill 1 or 2 processes? As you can see, even when trying to kill 2 events, only 5839 was killed.
Deluge may not be starting because of a different error. If you're getting the same error, try to `kill -9 $PID` (or `kill -KILL $PID`--same thing). If you are still having problems after that, post the new output of the deluge command (it won't survive a kill -9, so it will be a different problem).lifestyle wrote:Oh, and Deluge still refuses to start. I am going to reboot the system and see if makes any difference. Am I in Windows??
Sorry, that was my fault. I said kill number, because you should generally try to ask the process to shut down nicely before forcing the issue with a SIGKILL. Especially with deluge, which isn't very good at recovering from a SIGKILL (seems to screw up the persistent.state file every time).markybob wrote:i didnt say `kill NUMBER`, i said `kill -KILL NUMBER` ...you're not in windows, you just apparently cant read very well :p
