X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=2.8%2Flttng-docs-2.8.txt;h=35167a936675ad21811e55559bae9eda4a95125c;hb=85de609516bbb92d4428c86e502e34f8c96a474d;hp=3863c2be84fc0b225364583a288cd8438a3853ec;hpb=1188f085957b54aa101a2d53d54295ad1ff9f334;p=lttng-docs.git diff --git a/2.8/lttng-docs-2.8.txt b/2.8/lttng-docs-2.8.txt index 3863c2b..35167a9 100644 --- a/2.8/lttng-docs-2.8.txt +++ b/2.8/lttng-docs-2.8.txt @@ -1,7 +1,7 @@ The LTTng Documentation ======================= Philippe Proulx -v2.8, 8 December 2016 +v2.8, 20 February 2017 include::../common/copyright.txt[] @@ -888,8 +888,8 @@ sudo lttng create my-kernel-session --output=/tmp/my-kernel-trace -- [role="term"] ---- -lttng list --kernel -lttng list --kernel --syscall +sudo lttng list --kernel +sudo lttng list --kernel --syscall ---- -- @@ -6617,7 +6617,7 @@ remote system. See man:lttng-create(1) for the exact URL format. . On the target system, use the man:lttng(1) command-line tool as usual. When tracing is active, the target's consumer daemon sends sub-buffers - to the relay daemon running on the remote system intead of flushing + to the relay daemon running on the remote system instead of flushing them to the local file system. The relay daemon writes the received packets to the local file system. @@ -6864,7 +6864,7 @@ trace data after a system crash: -- [role="term"] ---- -lttng create --shm-path=/path/to/shm +lttng create my-session --shm-path=/path/to/shm ---- --