Solaris 调试工具.docVIP

/wiki/index.php/Processes Why should I monitor Processes? Monitoring process activity is a routine task during the administration of systems. Fortunately, a large number of tools examine process details, most of which make use of procfs. Many of these tools are suitable for troubleshooting application problems and for analyzing performance. [edit] Which Tools Should I use for Process Analysis? Since there are so many tools for process analysis, it can be helpful to group them into general categories. Overall status tools - The prstat command immediately provides a by-process indication of CPU and memory consumption. prstat can also fetch microstate accounting details and by-thread details. The original command for listing process status is ps, the output of which can be customized. Control tools - Various commands, such as pkill, pstop, prun and preap, control the state of a process. These commands can be used to repair application issues, especially runaway processes. Introspection tools - Numerous commands, such as pstack, pmap, pfiles, and pargs inspect process details. pmap and pfiles examine the memory and file resources of a process; pstack can view the stack backtrace of a process and its threads, providing a glimpse of which functions are currently running. Lock activity examination tools - Excessive lock activity and contention can be identified with the plockstat command and DTrace. Tracing tools - Tracing system calls and function calls provides the best insight into process behavior. Solaris provides tools including truss, apptrace, and dtrace to trace processes. The following table summarizes and cross-references the tools covered in this section. Tools for Process Analysis Tool Description prstat For viewing overall process status ps To print process status and information ptree To print a process ancestry tree pgrep; pkill To match a process name; to send a signal pstop; prun To freeze a process; to continue a process pw