From 51a225a5ce0bff31b367c0e5ef54feba5ba1d9c2 Mon Sep 17 00:00:00 2001 From: Philippe Proulx Date: Mon, 12 Nov 2018 15:56:38 -0500 Subject: [PATCH] Fix: 2.10: wildcards are supported anywhere in TP/syscall names Signed-off-by: Philippe Proulx --- 2.10/lttng-docs-2.10.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/2.10/lttng-docs-2.10.txt b/2.10/lttng-docs-2.10.txt index 1075640..bbcb247 100644 --- a/2.10/lttng-docs-2.10.txt +++ b/2.10/lttng-docs-2.10.txt @@ -5775,8 +5775,9 @@ Tracepoint or system call name. In the case of a Linux KProbe or function, this is a custom name given to the event rule. With the JUL, log4j, and Python domains, this is a logger name. -With a tracepoint, logger, or system call name, the last character -can be `*` to match anything that remains. +With a tracepoint, logger, or system call name, you can use the special +`*` globbing character to match anything (for example, `sched_*`, +`my_comp*:*msg_*`). |All. -- 2.34.1