Today I changed a few things in my kernel config around. I replaced SCHED_4BSD with SCHED_ULE, added PREEMPTION. I put some of the debugging features back in just incase I had any problems. I figure a little bit of overhead is a small price to pay. # Debugging for use in -current options KDB options DDB #Enable the kernel debugger options INVARIANTS #Enable calls of extra sanity checking options INVARIANT_SUPPORT #Extra sanity checks of internal structures, required by INVARIANTS #options WITNESS #Enable checks to detect deadlocks and cycles #options WITNESS_SKIPSPIN #Don't run witness on spinlocks for speed and I removed some drivers that I had built into the kernel (sound/network/etc) and use loadable modules now. Anyway, I rebooted with this new kernel, loaded mldonkey up, and went out with a friend to 7/11. ...taquitos... mhmmm. I got home about an hour later. mldonkey is not responding to me at all. So I tried to kill it... This is my problem: [incubus_at_elemental:~]$ ps aux | grep mlnet incubus 703 0.0 8.4 22576 20972 p1 RN+ 12:42AM 0:25.52 /usr/local/bin/mlnet-real [incubus_at_elemental:~]$ kill -9 703 [incubus_at_elemental:~]$ kill -9 703 [incubus_at_elemental:~]$ kill -9 703 [incubus_at_elemental:~]$ ps aux | grep mlnet incubus 703 0.0 8.4 22576 20972 p1 RN+ 12:42AM 0:25.52 /usr/local/bin/mlnet-real [incubus_at_elemental:~]$ su - otp-md5 496 el2739 ext Password: [root_at_elemental:~]$ kill -9 703 [root_at_elemental:~]$ kill -9 703 [root_at_elemental:~]$ kill -9 703 [root_at_elemental:~]$ kill -9 703 [root_at_elemental:~]$ kill -9 703 [root_at_elemental:~]$ exit logout [incubus_at_elemental:~]$ ps aux | grep mlnet incubus 703 0.0 8.4 22576 20972 p1 RN+ 12:42AM 0:25.52 /usr/local/bin/mlnet-realReceived on Fri Sep 17 2004 - 04:30:33 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:12 UTC