That proc r surge below is a bit suspicious. Somewhere where you have
space, start the following script loop:
while true; do ps auxwww >> myproctrace.txt; sleep 0.3; echo "### next
run" >>myproctrace.txt; done
The 0.3 sec is a bit of an overkill. This might slow down your system,
but if you manage to run this during the time the system is
unresponsive, you should be able to navigate from ps run to ps run using
the "###" string and see what on earth span all these processes so
quickly (Oracle?)
GM
Troy Knabe wrote:
Yes. 143 in the r column
143 0 0 33371968 615864 4991000 0 0 0 20 1510 5516
2 5 93 0 0
--
--
George Magklaras BSc Hons MPhil
RHCE:805008309135525
Senior Computer Systems Engineer/UNIX-Linux Systems Administrator
EMBnet Technical Management Board
The Biotechnology Centre of Oslo,
University of Oslo
http://folk.uio.no/georgios
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
