projects
/
lttng-tools.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
doc/man: xsl: move manpage-ulinks.xsl -> manpage-links.xsl
[lttng-tools.git]
/
doc
/
man
/
lttng-enable-event.1.txt
diff --git
a/doc/man/lttng-enable-event.1.txt
b/doc/man/lttng-enable-event.1.txt
index 4d88bdb1b6d37480287c796d1ba92c97942f7db6..b58691ba018c900a331fe2e29b3f7ff0d67af3f4 100644
(file)
--- a/
doc/man/lttng-enable-event.1.txt
+++ b/
doc/man/lttng-enable-event.1.txt
@@
-106,6
+106,7
@@
a _don't care_.
For example, consider the following commands:
For example, consider the following commands:
+[role="term"]
----------------------------------------------------------------
lttng enable-event --userspace hello:world
lttng enable-event --userspace hello:world --loglevel=TRACE_INFO
----------------------------------------------------------------
lttng enable-event --userspace hello:world
lttng enable-event --userspace hello:world --loglevel=TRACE_INFO
@@
-180,6
+181,10
@@
when creating a new event rule. If the filter expression evaluates
to true when executed against the dynamic values of an event's fields
when tracing, the filtering condition passes.
to true when executed against the dynamic values of an event's fields
when tracing, the filtering condition passes.
+NOTE: Make sure to **single-quote** the filter expression when running
+the command from a shell, as filter expressions typically include
+characters having a special meaning for most shells.
+
The filter expression syntax is very similar to C language conditional
expressions (expressions that can be evaluated by an `if` statement).
The filter expression syntax is very similar to C language conditional
expressions (expressions that can be evaluated by an `if` statement).
This page took
0.025232 seconds
and
5
git commands to generate.