summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorfche <fche>2006-04-10 18:41:17 +0000
committerfche <fche>2006-04-10 18:41:17 +0000
commit7abecb38074f26f8f22d40c85e9eb7846f15ca7d (patch)
tree6c4a7907684e92921fc1dbd2c1f27b420d6cc2c7
parentdc0b623a28b4185e155f16a9cf63a8f22c528b5f (diff)
downloadsystemtap-steved-7abecb38074f26f8f22d40c85e9eb7846f15ca7d.tar.gz
systemtap-steved-7abecb38074f26f8f22d40c85e9eb7846f15ca7d.tar.xz
systemtap-steved-7abecb38074f26f8f22d40c85e9eb7846f15ca7d.zip
* lower uppity functor language
-rw-r--r--stapprobes.5.in10
1 files changed, 5 insertions, 5 deletions
diff --git a/stapprobes.5.in b/stapprobes.5.in
index a268abd7..ba642a06 100644
--- a/stapprobes.5.in
+++ b/stapprobes.5.in
@@ -21,13 +21,13 @@ The following sections enumerate the variety of probe points supported
by the systemtap translator, and additional aliases defined by
standard tapset scripts.
.PP
-The general probe point syntax is a "dotted-functor" sequence. This
+The general probe point syntax is a dotted-symbol sequence. This
allows a breakdown of the event namespace into parts, somewhat like
the Domain Name System does on the Internet. Each component
-identifier may be parametrized by a string or number literal. A
-component part name may be replaced by a "*" character, to expand to
-other matching probe points. These are all syntactically valid probe
-points:
+identifier may be parametrized by a string or number literal, with a
+syntax like a function call. A component may be replaced by a "*"
+character, to expand to other matching probe points. These are all
+syntactically valid probe points:
.SAMPLE
kernel.function("foo").return
syscall(22)