Topic: how to identify which user is using a lot of CPU (Read 702 times)
Global Moderator Community Supporter?
Jedai Sword Master
Gender:
Posts: 6236
38242 credits Members referred : 374
It's time to use PHP5!
« on: Jun 10, 2007, 12:00:34 PM »
Hi,
I try to monitor frequently my server with "top" just to see how fast my server is after a number of tasks are running.
today I noticed that there are a lot of tasks using a lot of CPU, now I like to know which user (linux user) is using so much CPU with the service httpd.
but all tasks for the service httpd are for the user apache. how can I see for which user is the task with PID 9300 executed?
is there a more global log file? (checking all the access logs is not really fun)
Community Supporter?
OMG!I am geek
Gender:
Posts: 56
364 credits Members referred : 0
Schwa?
« Reply #7 on: Jan 03, 2008, 03:17:34 AM »
I did some searching - but I can't seem to find it - so I'm sorry if this is not completely helpful. I did attend a Zend conference where they talked about a module that some people add into PHP/apache. It allows you to see the current script being executed while using 'ps'. I don't know if that would be helpful. I'm sorry that I can't remember more details. I would suggest start searching for items like that. -aaron
Global Moderator Community Supporter?
Jedai Sword Master
Gender:
Posts: 6236
38242 credits Members referred : 374
I did some searching - but I can't seem to find it - so I'm sorry if this is not completely helpful. I did attend a Zend conference where they talked about a module that some people add into PHP/apache. It allows you to see the current script being executed while using 'ps'. I don't know if that would be helpful. I'm sorry that I can't remember more details. I would suggest start searching for items like that. -aaron
Ho aaron and welcome, yes right there is a module called su_php this way all tasks are exectuted by the user (the bad point is that compiling this module together with DireactAdmin is not a biginner task)
I use Apache status now to see what request is using a lot of resources and was able to indentify hackers very fast