On Thursday 08 December 2005 10:05, a tiny voice compelled Mark Knecht to write: > The problem I see periodically is that at time the java_vm will go to > 100% CPU and I have to kill it by hand.
After playing a couple hands of Omaha at pogo: ps ax | grep java 30537 ? S 0:01 java_vm 30538 ? S 0:00 java_vm 30539 ? S 0:09 java_vm 30540 ? S 0:00 java_vm 30541 ? S 0:00 java_vm 30542 ? S 0:00 java_vm 30543 ? S 0:00 java_vm 30544 ? S 0:01 java_vm 30545 ? S 0:00 java_vm 30547 ? S 0:07 java_vm 30549 ? S 0:00 java_vm 30550 ? S 0:00 java_vm 30551 ? S 0:00 java_vm 30554 ? S 0:00 java_vm 30555 ? S 0:00 java_vm 31005 ? S 0:00 java_vm 32240 pts/2 S+ 0:00 grep java About half of the individual instances died when I closed the tab I was using for pogo. -- Regards, Ernie 100% Microsoft and Intel free 10:37:03 up 17:09, 3 users, load average: 0.18, 0.42, 0.34 Linux 2.6.5-gentoo-r1 i686 AMD Athlon(tm) XP 2400+ -- gentoo-user@gentoo.org mailing list
