From f0e31baf0e49c3a5aaaddaa372cf33954b108190 Mon Sep 17 00:00:00 2001 From: ddomingo Date: Thu, 20 Nov 2008 09:35:43 +1000 Subject: changes as per tech review wcohen, run 1 --- doc/SystemTap_Beginners_Guide/en-US/Introduction.xml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'doc/SystemTap_Beginners_Guide/en-US/Introduction.xml') diff --git a/doc/SystemTap_Beginners_Guide/en-US/Introduction.xml b/doc/SystemTap_Beginners_Guide/en-US/Introduction.xml index dbca02fc..d63d7f8c 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Introduction.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Introduction.xml @@ -57,9 +57,12 @@ ** Short summary; when is SystemTap suitable vs other popular monitoring tools (e.g. top, Oprofile, /proc) + SystemTap was originally developed as a working ∏ version of old Linux probing tools such as dprobes and the Linux Trace Toolkit. SystemTap aims to supplement the existing suite of Linux monitoring tools by providing users with the infrastructure to track kernel activity. In addition, SystemTap combines this capability with two things: + + Flexibility: SystemTap's framework allows users to develop simple scripts for investigating and monitoring a wide variety of kernel functions, system calls, and other events that occur in kernel-space. With this, SystemTap is not soo much a tool as it is a system that allows you to develop your own kernel-specific forensic and monitoring tools. -- cgit