Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m developing a C++ application with process monitoring capabilities, which monitors state changes based on this model: http://www.macdesign.net/capella/it4813/images/stallings-Linux_process-thread_states-f4.18.png
However, as /proc/pid/status combines both the “ready” and “executing” states into “running”, I’m at a loss as to how I can find out which of these states a process is actually in. Can anyone offer any suggestions as to how I may discover this?
The question is malformed. On a single CPU, it’s literally never possible to see a process in the “running” state, because by definition the monitoring process has the CPU. If you really need fine-grained logging control over process transitions, you need to do it in the kernel (or at least with in-kernel support — see lttng or systemtap for tools that might help here). Tools for tracking CPU usage from userspace are more coarse-grained, either using the total usage numbers already tracked by the kernel (e.g.
/usr/bin/time) or by sampling the process table at intervals (bootchart works this way).