Using the explicit PID won't make a difference. This is from another
occurrence:
$ ps axl | grep amule
0 1000 2534 1 20 0 146528 53884 - Rl ? 302:26 amule
$ sudo kill -9 2534
$ sudo kill -9 2534
$ sudo kill -9 2534
$ ps axl | grep amule
0 1000 2534 1 20 0 146528 53892 - R ? 302:37 amule
Also the process is at 100%, which is quite inconvenient:
$ top -b | grep amule
2534 jano 20 0 143m 52m 18m R 98 1.5 305:55.66 amule
2534 jano 20 0 143m 52m 18m R 100 1.5 305:58.67 amule
2534 jano 20 0 143m 52m 18m R 100 1.5 306:01.67 amule
2534 jano 20 0 143m 52m 18m R 100 1.5 306:04.67 amule
2534 jano 20 0 143m 52m 18m R 100 1.5 306:07.68 amule
^C
--
Unresponsive process cannot be killed (sudo kill -9)
https://bugs.launchpad.net/bugs/665211
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
