diff -Nru ltt-control-2.13~pre/configure.ac ltt-control-2.13~pre/configure.ac --- ltt-control-2.13~pre/configure.ac 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/configure.ac 2021-06-17 15:47:40.000000000 +0000 @@ -426,28 +426,28 @@ # Command short descriptions _AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_ADD_CONTEXT], [Add context fields to be recorded]) _AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_ADD_TRIGGER], [Add a trigger]) -_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_CLEAR], [Clear a tracing session]) -_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_CREATE], [Create a tracing session]) -_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_DESTROY], [Destroy tracing sessions]) +_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_CLEAR], [Clear a recording session]) +_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_CREATE], [Create a recording session]) +_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_DESTROY], [Destroy recording sessions]) _AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_DISABLE_CHANNEL], [Disable channels]) _AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_DISABLE_EVENT], [Disable recording event rules]) -_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_DISABLE_ROTATION], [Unset a tracing session rotation schedule]) +_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_DISABLE_ROTATION], [Unset a recording session rotation schedule]) _AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_ENABLE_CHANNEL], [Create or enable a channel]) _AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_ENABLE_EVENT], [Create or enable recording event rules]) -_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_ENABLE_ROTATION], [Set a tracing session rotation schedule]) +_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_ENABLE_ROTATION], [Set a recording session rotation schedule]) _AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_HELP], [Show the help of a command]) -_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_LIST], [List tracing sessions and instrumentation points]) +_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_LIST], [List recording sessions and instrumentation points]) _AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_LIST_TRIGGERS], [List triggers]) -_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_LOAD], [Load tracing session configurations]) -_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_REGENERATE], [Regenerate specific tracing session data]) +_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_LOAD], [Load recording session configurations]) +_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_REGENERATE], [Regenerate specific recording session data]) _AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_REMOVE_TRIGGER], [Remove a trigger]) -_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_ROTATE], [Archive the current trace chunk of a tracing session]) -_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_SAVE], [Save tracing session configurations]) -_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_SET_SESSION], [Set the current tracing session]) -_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_SNAPSHOT], [Take a tracing session snapshot]) -_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_START], [Start a tracing session]) -_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_STATUS], [Show the status of the current tracing session]) -_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_STOP], [Stop a tracing session]) +_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_ROTATE], [Archive the current trace chunk of a recording session]) +_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_SAVE], [Save recording session configurations]) +_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_SET_SESSION], [Set the current recording session]) +_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_SNAPSHOT], [Take a recording session snapshot]) +_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_START], [Start a recording session]) +_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_STATUS], [Show the status of the current recording session]) +_AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_STOP], [Stop a recording session]) _AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_TRACK], [Allow specific processes to record events]) _AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_UNTRACK], [Disallow specific processes to record events]) _AC_DEFINE_QUOTED_AND_SUBST([CMD_DESCR_VERSION], [Show LTTng-tools version information]) @@ -864,19 +864,13 @@ [Disable the build of the extra components])) -# Always build libconfig since it a dependency of libcommon -build_lib_config=yes - -build_lib_compat=no build_lib_consumer=no -build_lib_hashtable=no build_lib_health=no build_lib_index=no build_lib_kernel_consumer=no build_lib_kernel_ctl=no build_lib_lttng_ctl=no build_lib_relayd=no -build_lib_fd_tracker=no build_lib_sessiond_comm=no build_lib_testpoint=no build_lib_ust_consumer=no @@ -911,12 +905,9 @@ [ build_lib_lttng_ctl=yes build_lib_sessiond_comm=yes - build_lib_hashtable=yes - build_lib_compat=yes build_lib_index=yes build_lib_health=yes build_lib_testpoint=yes - build_lib_fd_tracker=yes ] ) AS_IF([test x$enable_bin_lttng_sessiond != xno], @@ -924,8 +915,6 @@ build_lib_lttng_ctl=yes build_lib_sessiond_comm=yes build_lib_kernel_ctl=yes - build_lib_hashtable=yes - build_lib_compat=yes build_lib_relayd=yes build_lib_testpoint=yes build_lib_health=yes @@ -936,7 +925,6 @@ AS_IF([test x$build_lib_lttng_ctl = xyes], [ build_lib_sessiond_comm=yes - build_lib_hashtable=yes ] ) @@ -944,8 +932,6 @@ [ build_lib_sessiond_comm=yes build_lib_kernel_consumer=yes - build_lib_hashtable=yes - build_lib_compat=yes build_lib_relayd=yes AS_IF([test "x$with_lttng_ust" = "xyes"], [build_lib_ust_consumer=yes]) ] @@ -1040,17 +1026,13 @@ AM_CONDITIONAL([BUILD_EXTRAS], [test x$enable_extras != xno]) # Export libraries build conditions. -AM_CONDITIONAL([BUILD_LIB_COMPAT], [test x$build_lib_compat = xyes]) -AM_CONDITIONAL([BUILD_LIB_CONFIG], [test x$build_lib_config = xyes]) AM_CONDITIONAL([BUILD_LIB_CONSUMER], [test x$build_lib_consumer = xyes]) -AM_CONDITIONAL([BUILD_LIB_HASHTABLE], [test x$build_lib_hashtable = xyes]) AM_CONDITIONAL([BUILD_LIB_HEALTH], [test x$build_lib_health = xyes]) AM_CONDITIONAL([BUILD_LIB_INDEX], [test x$build_lib_index = xyes]) AM_CONDITIONAL([BUILD_LIB_KERNEL_CONSUMER], [test x$build_lib_kernel_consumer = xyes]) AM_CONDITIONAL([BUILD_LIB_KERNEL_CTL], [test x$build_lib_kernel_ctl = xyes]) AM_CONDITIONAL([BUILD_LIB_LTTNG_CTL], [test x$build_lib_lttng_ctl = xyes]) AM_CONDITIONAL([BUILD_LIB_RELAYD], [test x$build_lib_relayd = xyes]) -AM_CONDITIONAL([BUILD_LIB_FD_TRACKER], [test x$build_lib_fd_tracker = xyes]) AM_CONDITIONAL([BUILD_LIB_SESSIOND_COMM], [test x$build_lib_sessiond_comm = xyes]) AM_CONDITIONAL([BUILD_LIB_TESTPOINT], [test x$build_lib_testpoint = xyes]) AM_CONDITIONAL([BUILD_LIB_UST_CONSUMER], [test x$build_lib_ust_consumer = xyes]) diff -Nru ltt-control-2.13~pre/debian/changelog ltt-control-2.13~pre/debian/changelog --- ltt-control-2.13~pre/debian/changelog 2021-06-16 15:49:30.000000000 +0000 +++ ltt-control-2.13~pre/debian/changelog 2021-06-17 15:48:23.000000000 +0000 @@ -1,8 +1,8 @@ -ltt-control (2.13~pre-0+git6075+202106161549~ubuntu18.04.1) bionic; urgency=low +ltt-control (2.13~pre-0+git6085+202106171548~ubuntu18.04.1) bionic; urgency=low * Auto build. - -- Michael Jeanson Wed, 16 Jun 2021 15:49:30 +0000 + -- Ubuntu LTTng Thu, 17 Jun 2021 15:48:23 +0000 llttng-tools (2.13~pre-0-lttng1) unstable; urgency=medium diff -Nru ltt-control-2.13~pre/debian/git-build-recipe.manifest ltt-control-2.13~pre/debian/git-build-recipe.manifest --- ltt-control-2.13~pre/debian/git-build-recipe.manifest 2021-06-16 15:49:30.000000000 +0000 +++ ltt-control-2.13~pre/debian/git-build-recipe.manifest 2021-06-17 15:48:23.000000000 +0000 @@ -1,3 +1,3 @@ -# git-build-recipe format 0.4 deb-version {debupstream}+git6075+202106161549 -lp:lttng-tools git-commit:a8940c5eb1046e84c10bb0cf72c0f2575a8c9e4e +# git-build-recipe format 0.4 deb-version {debupstream}+git6085+202106171548 +lp:lttng-tools git-commit:878fea902b1c509b61be1f18494edb1f647733b4 nest packaging lp:~lttng/lttng-tools/+git/packaging debian git-commit:df7fd3f3534a3eef31389b31d76977f691592bf9 diff -Nru ltt-control-2.13~pre/doc/examples/Makefile.am ltt-control-2.13~pre/doc/examples/Makefile.am --- ltt-control-2.13~pre/doc/examples/Makefile.am 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/examples/Makefile.am 2021-06-17 15:47:40.000000000 +0000 @@ -1,3 +1,5 @@ # SPDX-License-Identifier: GPL-2.0-only +if BUILD_LIB_LTTNG_CTL SUBDIRS = rotation trigger-condition-event-matches +endif diff -Nru ltt-control-2.13~pre/doc/examples/rotation/rotate-client-example.c ltt-control-2.13~pre/doc/examples/rotation/rotate-client-example.c --- ltt-control-2.13~pre/doc/examples/rotation/rotate-client-example.c 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/examples/rotation/rotate-client-example.c 2021-06-17 15:47:40.000000000 +0000 @@ -53,7 +53,7 @@ int ret; struct lttng_domain dom; struct lttng_event ev; - struct lttng_handle *chan_handle; + struct lttng_handle *chan_handle = NULL; printf("Creating session %s\n", session_name); ret = lttng_create_session(session_name, path); @@ -90,11 +90,10 @@ goto end; } - lttng_destroy_handle(chan_handle); - ret = 0; end: + lttng_destroy_handle(chan_handle); return ret; } diff -Nru ltt-control-2.13~pre/doc/man/common-daemon-cfg.txt ltt-control-2.13~pre/doc/man/common-daemon-cfg.txt --- ltt-control-2.13~pre/doc/man/common-daemon-cfg.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/common-daemon-cfg.txt 2021-06-17 15:47:40.000000000 +0000 @@ -21,7 +21,7 @@ Key:: The long name of a command-line option to set (see the - <> section below). + ``<>'' section below). Value:: The selected command-line option accepts an argument::: diff -Nru ltt-control-2.13~pre/doc/man/common-footer.txt ltt-control-2.13~pre/doc/man/common-footer.txt --- ltt-control-2.13~pre/doc/man/common-footer.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/common-footer.txt 2021-06-17 15:47:40.000000000 +0000 @@ -17,7 +17,7 @@ LTTng-tools is distributed under the http://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html[GNU General -Public License version 2]. See the +Public License version{nbsp}2]. See the https://github.com/lttng/lttng-tools/blob/master/LICENSE[`LICENSE`] file for details. diff -Nru ltt-control-2.13~pre/doc/man/common-lttng-cmd-after-options.txt ltt-control-2.13~pre/doc/man/common-lttng-cmd-after-options.txt --- ltt-control-2.13~pre/doc/man/common-lttng-cmd-after-options.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/common-lttng-cmd-after-options.txt 2021-06-17 15:47:40.000000000 +0000 @@ -36,7 +36,7 @@ nloption:--help option) instead of `/usr/bin/man`. `LTTNG_SESSION_CONFIG_XSD_PATH`:: - Path to the directory containing the `session.xsd` tracing session + Path to the directory containing the `session.xsd` recording session configuration XML schema. `LTTNG_SESSIOND_PATH`:: @@ -53,9 +53,9 @@ `$LTTNG_HOME/.lttngrc`:: Unix user's LTTng runtime configuration. + -This is where LTTng stores the name of the Unix user's current tracing +This is where LTTng stores the name of the Unix user's current recording session between executions of man:lttng(1). man:lttng-create(1) and -man:lttng-set-session(1) set the current tracing session. +man:lttng-set-session(1) set the current recording session. `$LTTNG_HOME/lttng-traces`:: Default output directory of LTTng traces in local and snapshot @@ -68,11 +68,11 @@ Unix user's LTTng runtime and configuration directory. `$LTTNG_HOME/.lttng/sessions`:: - Default directory containing the Unix user's saved tracing session + Default directory containing the Unix user's saved recording session configurations (see man:lttng-save(1) and man:lttng-load(1)). +{system_sessions_dir}+:: - Directory containing the system-wide saved tracing session + Directory containing the system-wide saved recording session configurations (see man:lttng-save(1) and man:lttng-load(1)). NOTE: `$LTTNG_HOME` defaults to the value of the `HOME` environment diff -Nru ltt-control-2.13~pre/doc/man/lttng.1.txt ltt-control-2.13~pre/doc/man/lttng.1.txt --- ltt-control-2.13~pre/doc/man/lttng.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,6 +1,6 @@ lttng(1) ======== -:revdate: 12 May 2021 +:revdate: 14 June 2021 NAME @@ -25,8 +25,8 @@ listening LTTng session daemon (man:lttng-sessiond(8)). A session daemon: -* Manages tracing sessions (see man:lttng-concepts(7) to learn more - about tracing sessions). +* Manages recording sessions (see man:lttng-concepts(7) to learn more + about recording sessions). * Controls the various components (like tracers and consumer daemons) of LTTng. @@ -67,7 +67,7 @@ of LTTng. The `lttng` tool offers a subcommand-based command-line interface. The -<> section below lists the available commands. +``<>'' section below lists the available commands. Session daemon connection @@ -185,8 +185,8 @@ The following commands also have their own nloption:--help option. -Tracing session -~~~~~~~~~~~~~~~ +Recording session +~~~~~~~~~~~~~~~~~ [options="header"] |=== |Command |Description diff -Nru ltt-control-2.13~pre/doc/man/lttng-add-context.1.txt ltt-control-2.13~pre/doc/man/lttng-add-context.1.txt --- ltt-control-2.13~pre/doc/man/lttng-add-context.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-add-context.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,6 +1,6 @@ lttng-add-context(1) ==================== -:revdate: 6 May 2021 +:revdate: 14 June 2021 NAME @@ -34,22 +34,22 @@ records of: + With the option:--session='SESSION' option::: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. Without the option:--session option::: - The current tracing session (see man:lttng-concepts(7) to learn more - about the current tracing session). + The current recording session (see man:lttng-concepts(7) to learn + more about the current recording session). With the option:--channel='CHANNEL'::: The channel named 'CHANNEL'. Without the option:--channel option::: - *All* the channels of the selected tracing session. + *All* the channels of the selected recording session. With the option:--list option:: List the available context field types. -See man:lttng-concepts(7) to learn more about tracing sessions and +See man:lttng-concepts(7) to learn more about recording sessions and channels. Repeat the option:--type='TYPE' option to add more than one context @@ -109,10 +109,11 @@ variable substitution in most shells. NOTE: As of LTTng{nbsp}{lttng_version}, you may :not: add context fields -to be recorded to the event records of a given channel once its tracing -session has been started (see man:lttng-start(1)) at least once. +to be recorded to the event records of a given channel once its +recording session has been started (see man:lttng-start(1)) at least +once. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. include::common-lttng-cmd-options-head.txt[] @@ -144,12 +145,12 @@ option:-c 'CHANNEL', option:--channel='CHANNEL':: Add context fields to be recorded to the event records of a channel named 'CHANNEL' instead of all the channels of the selected - tracing session. + recording session. option:-s 'SESSION', option:--session='SESSION':: Add context fields to be recorded to the event records of one or - more channels of the tracing session named 'SESSION' instead of the - current tracing session. + more channels of the recording session named 'SESSION' instead of + the current recording session. Context field type @@ -185,7 +186,7 @@ ---- ==== -.Add a single statically-known context field to be recorded to all the Linux kernel channels of the current tracing session. +.Add a single statically-known context field to be recorded to all the Linux kernel channels of the current recording session. ==== [role="term"] ---- @@ -193,7 +194,7 @@ ---- ==== -.Add three statically-known context fields to be recorded to a specific user space channel of a specific tracing session. +.Add three statically-known context fields to be recorded to a specific user space channel of a specific recording session. ==== See the option:--session and option:--channel options. @@ -205,7 +206,7 @@ ---- ==== -.Add a perf counter context field to be recorded to a specific Linux kernel channel of the current tracing session. +.Add a perf counter context field to be recorded to a specific Linux kernel channel of the current recording session. ==== See the option:--channel option. @@ -216,7 +217,7 @@ ---- ==== -.Add an LTTng application-specific context field to be recorded to all the JUL channels of the current tracing session. +.Add an LTTng application-specific context field to be recorded to all the JUL channels of the current recording session. ==== [role="term"] ---- diff -Nru ltt-control-2.13~pre/doc/man/lttng-add-trigger.1.txt ltt-control-2.13~pre/doc/man/lttng-add-trigger.1.txt --- ltt-control-2.13~pre/doc/man/lttng-add-trigger.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-add-trigger.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,6 +1,6 @@ lttng-add-trigger(1) ==================== -:revdate: 6 May 2021 +:revdate: 14 June 2021 NAME @@ -35,7 +35,7 @@ specifiers>>. The order of the action specifiers is significant: LTTng attempts to execute the actions of a firing trigger in this order. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. List the triggers of your Unix user, or of all users if your Unix user is `root`, with the man:lttng-list-triggers(1) command. @@ -71,11 +71,11 @@ ('ERSPEC' part). + Capture event record and context fields with one or more -nloption:--capture options (see the <> -section below to learn more). When an `event-rule-matches` condition -with capture descriptors is satisfied, the captured field values are -available in the evaluation object of the condition using the -liblttng-ctl C{nbsp}API. +nloption:--capture options (see the ``<>'' section below to learn more). When an +`event-rule-matches` condition with capture descriptors is satisfied, +the captured field values are available in the evaluation object of the +condition using the liblttng-ctl C{nbsp}API. + IMPORTANT: Make sure to **single-quote** 'CDESCR' when you run the `add-trigger` command from a shell, as capture descriptors can include @@ -178,65 +178,66 @@ + See below for the nloption:--rate-policy option. -Start a tracing session:: +Start a recording session:: Synopsis: + [verse] option:--action=**start-session** 'SESSION' [nloption:--rate-policy='POLICY'] {nbsp} + -Starts the tracing session named 'SESSION' like man:lttng-start(1) +Starts the recording session named 'SESSION' like man:lttng-start(1) would. + -If no tracing session has the name 'SESSION' when LTTng is ready to +If no recording session has the name 'SESSION' when LTTng is ready to execute the action, LTTng does nothing. + See below for the nloption:--rate-policy option. -Stop a tracing session:: +Stop a recording session:: Synopsis: + [verse] option:--action=**stop-session** 'SESSION' [nloption:--rate-policy='POLICY'] {nbsp} + -Stops the tracing session named 'SESSION' like man:lttng-stop(1) would. +Stops the recording session named 'SESSION' like man:lttng-stop(1) +would. + -If no tracing session has the name 'SESSION' when LTTng is ready to +If no recording session has the name 'SESSION' when LTTng is ready to execute the action, LTTng does nothing. + See below for the nloption:--rate-policy option. -Rotate a tracing session:: +Rotate a recording session:: Synopsis: + [verse] option:--action=**rotate-session** 'SESSION' [nloption:--rate-policy='POLICY'] {nbsp} + -Archives the current trace chunk of the tracing session named 'SESSION' -like man:lttng-rotate(1) would. +Archives the current trace chunk of the recording session named +'SESSION' like man:lttng-rotate(1) would. + -If no tracing session has the name 'SESSION' when LTTng is ready to +If no recording session has the name 'SESSION' when LTTng is ready to execute the action, LTTng does nothing. + See below for the nloption:--rate-policy option. -Take a tracing session snapshot:: +Take a recording session snapshot:: Synopsis: + [verse] option:--action=**snapshot-session** 'SESSION' [nloption:--rate-policy='POLICY'] {nbsp} + -Takes a snapshot of the tracing session named 'SESSION' like +Takes a snapshot of the recording session named 'SESSION' like man:lttng-snapshot(1) would. + -When the condition of the trigger is satisfied, the tracing session -named 'SESSION', if any, must be a snapshot-mode tracing session +When the condition of the trigger is satisfied, the recording session +named 'SESSION', if any, must be a snapshot-mode recording session (see man:lttng-create(1)). + -If no tracing session has the name 'SESSION' when LTTng is ready to +If no recording session has the name 'SESSION' when LTTng is ready to execute the action, LTTng does nothing. + See below for the nloption:--rate-policy option. @@ -294,12 +295,14 @@ option:--condition='CONDTYPE':: Introductory option for a condition specifier of type 'CONDTYPE'. + -See the <> section above to learn more. +See the ``<>'' section above to learn +more. option:--action='ACTTYPE':: Introductory option for an action specifier of type 'ACTTYPE'. + -See the <> section above to learn more. +See the ``<>'' section above to learn +more. include::common-lttng-cmd-help-options.txt[] @@ -320,12 +323,12 @@ [role="term"] ---- $ lttng add-trigger --condition=event-rule-matches \ - --domain=kernel --type=syscall:entry \ + --type=syscall:entry \ --name='exec*' --action=notify ---- ==== -.Add an ``event rule matches'' trigger of which the action is to stop a tracing session and then rotate it. +.Add an ``event rule matches'' trigger of which the action is to stop a recording session and then rotate it. ==== The `event-rule-matches` trigger condition below specifies an event rule which matches any user space tracepoint event with a name starting with @@ -336,13 +339,13 @@ [role="term"] ---- $ lttng add-trigger --condition=event-rule-matches \ - --domain=user --name='my_app:*' \ + --type=user --name='my_app:*' \ --log-level=TRACE_WARNING.. \ --action=stop-session my-session \ --action=rotate-session my-session ---- -See man:lttng-concepts(7) to learn more about tracing sessions and +See man:lttng-concepts(7) to learn more about recording sessions and rotations. ==== @@ -361,7 +364,7 @@ ---- $ lttng add-trigger --name=my-trigger \ --condition=event-rule-matches \ - --domain=python --name=my-logger \ + --type=python --name=my-logger \ --action=snapshot-session my-session ---- ==== @@ -379,7 +382,7 @@ ---- # lttng add-trigger --owner-uid=$(id --user mireille) \ --condition=event-rule-matches \ - --domain=kernel --name='sched*' \ + --type=kernel --name='sched*' \ --action=notify ---- ==== @@ -394,12 +397,12 @@ [role="term"] ---- $ lttng add-trigger --condition=event-rule-matches \ - --domain=user --action=notify \ + --type=user --action=notify \ --rate-policy=every:10 ---- ==== -.Add an ``event rule matches'' trigger with a tracing session starting action to be executed a single time after 40{nbsp}times. +.Add an ``event rule matches'' trigger with a recording session starting action to be executed a single time after 40{nbsp}times. ==== The `event-rule-matches` trigger condition below specifies an event rule which matches any Linux system call event (entry and exit) of which the @@ -410,8 +413,7 @@ [role="term"] ---- $ lttng add-trigger --condition=event-rule-matches \ - --domain=kernel --type=syscall \ - --filter='fd < 3' \ + --type=syscall --filter='fd < 3' \ --action=start-session my-session \ --rate-policy=once-after:40 ---- diff -Nru ltt-control-2.13~pre/doc/man/lttng-clear.1.txt ltt-control-2.13~pre/doc/man/lttng-clear.1.txt --- ltt-control-2.13~pre/doc/man/lttng-clear.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-clear.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,10 +1,10 @@ lttng-clear(1) ============== -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME ---- -lttng-clear - Clear an LTTng tracing session +lttng-clear - Clear an LTTng recording session SYNOPSIS @@ -15,46 +15,47 @@ DESCRIPTION ----------- -The `lttng clear` command clears one or more tracing sessions, that is, -it deletes the contents of their tracing buffers and of all their local -and streamed trace data. +The `lttng clear` command clears one or more recording sessions, that +is, it deletes the contents of their recording buffers and of all their +local and streamed trace data. -See man:lttng-concepts(7) to learn more about tracing sessions. +See man:lttng-concepts(7) to learn more about recording sessions. The `clear` command clears: Without any option:: - The current tracing session. + The current recording session. + -See man:lttng-concepts(7) to learn more about the current tracing +See man:lttng-concepts(7) to learn more about the current recording session. With the 'SESSION' argument:: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. With the option:--all option:: - *All* the tracing sessions of the connected session daemon for your - Unix user, or for all users if your Unix user is `root`, as listed - in the output of `lttng list` (see man:lttng-list(1)). + *All* the recording sessions of the connected session daemon for + your Unix user, or for all users if your Unix user is `root`, as + listed in the output of `lttng list` (see man:lttng-list(1)). + See the ``Session daemon connection'' section of man:lttng(1) to learn how a user application connects to a session daemon. -If a tracing session is configured in snapshot mode (see the +If a recording session is configured in snapshot mode (see the nloption:--snapshot option of the man:lttng-create(1) command), the -`clear` command only clears the tracing buffers. +`clear` command only clears the recording buffers. -For a given tracing session, if at least one rotation occurred (see -man:lttng-concepts(7)), the `clear` command only clears its tracing +For a given recording session, if at least one rotation occurred (see +man:lttng-concepts(7)), the `clear` command only clears its recording buffers and its current trace chunk, :not: its archived trace chunks. NOTE: The nloption:--disallow-clear option and the `LTTNG_RELAYD_DISALLOW_CLEAR` environment variable of man:lttng-relayd(8) can disable remote clearing operations. If LTTng -sends tracing data over the network for the selected tracing session(s) -to an LTTng relay daemon configured as such, the `clear` command fails. +sends recording data over the network for the selected recording +session(s) to an LTTng relay daemon configured as such, the `clear` +command fails. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. include::common-lttng-cmd-options-head.txt[] @@ -63,10 +64,10 @@ Recording target ~~~~~~~~~~~~~~~~ option:-a, option:--all:: - Clear all the tracing sessions of your Unix user, or of all users if + Clear all the recording sessions of your Unix user, or of all users if your Unix user is `root`, as listed in the output of - man:lttng-list(1), instead of the current tracing session or the - tracing session named 'SESSION'. + man:lttng-list(1), instead of the current recording session or the + recording session named 'SESSION'. include::common-lttng-cmd-help-options.txt[] @@ -78,7 +79,7 @@ [[examples]] EXAMPLES -------- -.Clear the current tracing session. +.Clear the current recording session. ==== [role="term"] ---- @@ -86,7 +87,7 @@ ---- ==== -.Clear a specific tracing session. +.Clear a specific recording session. ==== [role="term"] ---- @@ -94,7 +95,7 @@ ---- ==== -.Clear all tracing sessions. +.Clear all recording sessions. ==== See the option:--all option. diff -Nru ltt-control-2.13~pre/doc/man/lttng-concepts.7.txt ltt-control-2.13~pre/doc/man/lttng-concepts.7.txt --- ltt-control-2.13~pre/doc/man/lttng-concepts.7.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-concepts.7.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,8 +1,8 @@ lttng-concepts(7) ================= -:revdate: 3 May 2021 +:revdate: 14 June 2021 :sect-event-rule: INSTRUMENTATION POINT, EVENT RULE, AND EVENT -:sect-session: TRACING SESSION +:sect-session: RECORDING SESSION :sect-domain: TRACING DOMAIN :sect-channel: CHANNEL AND RING BUFFER :sect-recording-event-rule: RECORDING EVENT RULE AND EVENT RECORD @@ -25,7 +25,7 @@ * Instrumentation point, event rule, and event * Trigger -* Tracing session +* Recording session * Tracing domain * Channel and ring buffer * Recording event rule and event record @@ -38,8 +38,8 @@ which, when executed, creates an LTTng _event_. LTTng offers various types of instrumentation; see the -<> section below to learn -about them. +``<>'' section below to +learn about them. An _event rule_ is a set of conditions to match a set of events. @@ -61,27 +61,27 @@ evaluate the arguments of the instrumentation point. In practice, LTTng implements various optimizations for the Linux kernel -and user space tracing domains (see the <> section -below) to avoid actually creating an event -when the tracer knows, thanks to properties which are independent from -the event payload and current context, that it would never emit such an -event. Those properties are: +and user space tracing domains (see the ``<>'' +section below) to avoid actually creating an event when the tracer +knows, thanks to properties which are independent from the event payload +and current context, that it would never emit such an event. Those +properties are: * The instrumentation point type (see the - <> section below). + ``<>'' section below). * The instrumentation point name. * The instrumentation point log level. * For a recording event rule (see the - <> section + ``<>'' section below): ** The status of the rule itself. -** The status of the channel (see the <> section - below). -** The activity of the tracing session (started or stopped; see - the <> section below). +** The status of the channel (see the ``<>'' + section below). +** The activity of the recording session (started or stopped; see + the ``<>'' section below). ** Whether or not the process for which LTTng would create the event is allowed to record events (see man:lttng-track(1)). @@ -98,20 +98,20 @@ A specific type of event rule of which the action is to record the matched event as an event record. + -See the <> section +See the ``<>'' section below. + Create or enable a recording event rule with the man:lttng-enable-event(1) command. + -List the recording event rules of a specific tracing session +List the recording event rules of a specific recording session and/or channel with the man:lttng-list(1) and man:lttng-status(1) commands. ``Event rule matches'' <> condition (since LTTng{nbsp}2.13):: When the event rule of the trigger condition matches an event, LTTng can execute user-defined actions such as sending an LTTng - notification, starting a tracing session, and more. + notification, starting a recording session, and more. + See man:lttng-add-trigger(1) and man:lttng-event-rule(7). @@ -121,7 +121,8 @@ * The instrumentation point from which LTTng creates{nbsp}__E__ has a specific type. + -See the <> section below. +See the ``<>'' section +below. * A pattern matches the name of{nbsp}__E__ while another pattern doesn't. @@ -134,7 +135,7 @@ satisfy a filter expression. A recording event rule has additional, implicit conditions to satisfy. -See the <> section +See the ``<>'' section below to learn more. @@ -143,7 +144,7 @@ ~~~~~~~~~~~~~~~~~~~~~~~~~~~ As of LTTng{nbsp}{lttng_version}, the available instrumentation point types are, depending on the tracing domain (see the -<> section below): +``<>'' section below): Linux kernel:: LTTng tracepoint::: @@ -222,20 +223,20 @@ Conditions:: + -* The consumed buffer size of a given tracing - session (see the <> section below) +* The consumed buffer size of a given recording + session (see the ``<>'' section below) becomes greater than some value. * The buffer usage of a given channel (see the - <> section below) becomes greater than some - value. + ``<>'' section below) becomes greater than + some value. * The buffer usage of a given channel becomes less than some value. -* There's an ongoing tracing session rotation (see the - <> section below). +* There's an ongoing recording session rotation (see the + ``<>'' section below). -* A tracing session rotation becomes completed. +* A recording session rotation becomes completed. * An event rule matches an event. + @@ -246,15 +247,15 @@ Actions:: + * Send a notification to a user application. -* Start a given tracing session, like man:lttng-start(1) would do. -* Stop a given tracing session, like man:lttng-stop(1) would do. -* Archive the current trace chunk of a given tracing session (rotate), +* Start a given recording session, like man:lttng-start(1) would do. +* Stop a given recording session, like man:lttng-stop(1) would do. +* Archive the current trace chunk of a given recording session (rotate), like man:lttng-rotate(1) would do. -* Take a snapshot of a given tracing session, like man:lttng-snapshot(1) - would do. +* Take a snapshot of a given recording session, like + man:lttng-snapshot(1) would do. A trigger belongs to a session daemon (see man:lttng-sessiond(8)), not -to a specific tracing session. For a given session daemon, each Unix +to a specific recording session. For a given session daemon, each Unix user has its own, private triggers. Note, however, that the `root` Unix user may, for the root session daemon: @@ -278,12 +279,12 @@ [[session]] {sect-session} -------------- -A _tracing session_ is a stateful dialogue between you and a session -daemon (see man:lttng-sessiond(8)) for everything related to event -recording. +A _recording session_ (named ``tracing session'' prior to +LTTng{nbsp}2.13) is a stateful dialogue between you and a session daemon +(see man:lttng-sessiond(8)) for everything related to event recording. Everything that you do when you control LTTng tracers to record events -happens within a tracing session. In particular, a tracing session: +happens within a recording session. In particular, a recording session: * Has its own name, unique for a given session daemon. @@ -291,64 +292,64 @@ * Has its own state of activity (started or stopped). + -An active tracing session is an implicit recording event rule condition -(see the <> section -below). +An active recording session is an implicit recording event rule +condition (see the +``<>'' section below). * Has its own mode (local, network streaming, snapshot, or live). + -See the <> section below to learn -more. +See the ``<>'' section below to +learn more. -* Has its own channels (see the <> section +* Has its own channels (see the ``<>'' section below) to which are attached their own recording event rules. * Has its own process attribute inclusion sets (see man:lttng-track(1)). Those attributes and objects are completely isolated between different -tracing sessions. +recording sessions. -A tracing session is like an ATM session: the operations you do on the +A recording session is like an ATM session: the operations you do on the banking system through the ATM don't alter the data of other users of the same system. In the case of the ATM, a session lasts as long as your -bank card is inside. In the case of LTTng, a tracing session lasts from +bank card is inside. In the case of LTTng, a recording session lasts from the man:lttng-create(1) command to the man:lttng-destroy(1) command. -A tracing session belongs to a session daemon (see +A recording session belongs to a session daemon (see man:lttng-sessiond(8)). For a given session daemon, each Unix user has -its own, private tracing sessions. Note, however, that the `root` Unix -user may operate on or destroy another user's tracing session. +its own, private recording sessions. Note, however, that the `root` Unix +user may operate on or destroy another user's recording session. -Create a tracing session with the man:lttng-create(1) command. +Create a recording session with the man:lttng-create(1) command. -List the tracing sessions of the connected session daemon with +List the recording sessions of the connected session daemon with the man:lttng-list(1) command. -Start and stop a tracing session with the man:lttng-start(1) and +Start and stop a recording session with the man:lttng-start(1) and man:lttng-stop(1) commands. -Save and load a tracing session with the man:lttng-save(1) and +Save and load a recording session with the man:lttng-save(1) and man:lttng-load(1) commands. -Archive the current trace chunk of (rotate) a tracing session with the +Archive the current trace chunk of (rotate) a recording session with the man:lttng-rotate(1) command. -Destroy a tracing session with the man:lttng-destroy(1) command. +Destroy a recording session with the man:lttng-destroy(1) command. -Current tracing session +Current recording session ~~~~~~~~~~~~~~~~~~~~~~~ When you run the man:lttng-create(1) command, LTTng creates the `$LTTNG_HOME/.lttngrc` file if it doesn't exist (`$LTTNG_HOME` defaults to `$HOME`). -`$LTTNG_HOME/.lttngrc` contains the name of the _current tracing +`$LTTNG_HOME/.lttngrc` contains the name of the _current recording session_. -When you create a new tracing session with the `create` command, LTTng -updates the current tracing session. +When you create a new recording session with the `create` command, LTTng +updates the current recording session. -The following man:lttng(1) commands select the current tracing session +The following man:lttng(1) commands select the current recording session if you don't specify one: * man:lttng-add-context(1) @@ -371,15 +372,15 @@ * man:lttng-untrack(1) * man:lttng-view(1) -Set the current tracing session manually with the +Set the current recording session manually with the man:lttng-set-session(1) command, without having to edit the `.lttngrc` file. [[session-modes]] -Tracing session modes -~~~~~~~~~~~~~~~~~~~~~ -LTTng offers four tracing session modes: +Recording session modes +~~~~~~~~~~~~~~~~~~~~~~~ +LTTng offers four recording session modes: Local mode:: Write the trace data to the local file system. @@ -393,16 +394,16 @@ listening relay daemon (man:lttng-relayd(8)) when LTTng takes a snapshot. + -LTTng forces all the channels (see the <> +LTTng forces all the channels (see the ``<>'' section below) to be created to be configured to be snapshot-ready. + -LTTng takes a snapshot of such a tracing session when: +LTTng takes a snapshot of such a recording session when: + -- * You run the man:lttng-snapshot(1) command. * LTTng executes a `snapshot-session` trigger action (see the - <> section above). + ``<>'' section above). -- Live mode:: @@ -410,33 +411,33 @@ (see man:lttng-relayd(8)) for live reading. + An LTTng live reader (for example, man:babeltrace2(1)) can connect to -the same relay daemon to receive trace data while the tracing session is +the same relay daemon to receive trace data while the recording session is active. [[rotation]] -Tracing session rotation -~~~~~~~~~~~~~~~~~~~~~~~~ -A _tracing session rotation_ is the action of archiving the current -trace chunk of the tracing session to the file system. +Recording session rotation +~~~~~~~~~~~~~~~~~~~~~~~~~~ +A _recording session rotation_ is the action of archiving the current +trace chunk of the recording session to the file system. Once LTTng archives a trace chunk, it does :not: manage it anymore: you can read it, modify it, move it, or remove it. An _archived trace chunk_ is a collection of metadata and data stream files which form a self-contained LTTng trace. See the -<> section below to learn how +``<>'' section below to learn how LTTng names a trace chunk archive directory. -The _current trace chunk_ of a given tracing session includes: +The _current trace chunk_ of a given recording session includes: * The stream files which LTTng already wrote to the file system, and which are not part of a previously archived trace chunk, since the most recent event amongst: -** The first time the tracing session was started, either with the +** The first time the recording session was started, either with the man:lttng-start(1) command or with a `start-session` trigger action - (see the <> section above). + (see the ``<>'' section above). ** The last rotation, performed with: @@ -446,17 +447,17 @@ man:lttng-enable-rotation(1). *** An executed `rotate-session` trigger action (see the - <> section above). + ``<>'' section above). * The content of all the non-flushed sub-buffers of the channels of the - tracing session. + recording session. [[trace-chunk-naming]] Trace chunk archive naming ~~~~~~~~~~~~~~~~~~~~~~~~~~ A trace chunk archive is a subdirectory of the `archives` subdirectory -within the output directory of a tracing session (see the +within the output directory of a recording session (see the nloption:--output option of the man:lttng-create(1) command and of man:lttng-relayd(8)). @@ -468,15 +469,15 @@ * A self-contained LTTng trace. * A member of a set of trace chunk archives which form the complete - trace of a tracing session. + trace of a recording session. -In other words, an LTTng trace reader can read both the tracing +In other words, an LTTng trace reader can read both the recording session output directory (all the trace chunk archives), or a single trace chunk archive. -When LTTng performs a tracing session rotation, it names the resulting +When LTTng performs a recording session rotation, it names the resulting trace chunk archive as such, relative to the output directory of the -tracing session: +recording session: [verse] archives/__BEGIN__-__END__-__ID__ @@ -498,7 +499,7 @@ Example: `20180118T152407+0930` __ID__:: - Unique numeric identifier of the trace chunk within its tracing + Unique numeric identifier of the trace chunk within its recording session. Trace chunk archive name example: @@ -522,23 +523,23 @@ |Tracing domain |``Event rule matches'' trigger condition option |Option for other CLI commands |Linux kernel -|nloption:--domain=++kernel++ +|nloption:--type option starts with `kernel:` |nloption:--kernel |User space -|nloption:--domain=++user++ +|nloption:--type option starts with `user:` |nloption:--userspace |`java.util.logging` (JUL) -|nloption:--domain=++jul++ +|nloption:--type option starts with `jul:` |nloption:--jul |Apache log4j -|nloption:--domain=++log4j++ +|nloption:--type option starts with `log4j:` |nloption:--log4j |Python -|nloption:--domain=++python++ +|nloption:--type option starts with `python:` |nloption:--python |=== @@ -546,11 +547,11 @@ using some man:lttng(1) commands to avoid ambiguity. For example, because the Linux kernel and user space tracing domains support named tracepoints as instrumentation points (see the -<<"event-rule","{sect-event-rule}">> section above), you need to specify -a tracing domain when you create an event rule because both tracing -domains could have tracepoints sharing the same name. +``<<"event-rule","{sect-event-rule}">>'' section above), you need to +specify a tracing domain when you create an event rule because both +tracing domains could have tracepoints sharing the same name. -You can create channels (see the <> section +You can create channels (see the ``<>'' section below) in the Linux kernel and user space tracing domains. The other tracing domains have a single, default channel. @@ -562,7 +563,7 @@ Each ring buffer is divided into multiple _sub-buffers_. When a recording event rule (see the -<>'' section below) matches an event, LTTng can record it to one or more sub-buffers of one or more channels. @@ -571,28 +572,29 @@ * Its buffering scheme. + -See the <> section below. +See the ``<>'' section below. * What to do when there's no space left for a new event record because all sub-buffers are full. + -See the <> section below. +See the ``<>'' section +below. * The size of each ring buffer and how many sub-buffers a ring buffer has. + -See the <> section -below. +See the ``<>'' +section below. * The size of each trace file LTTng writes for this channel and the maximum count of trace files. + -See the <> section below. +See the ``<>'' section below. * The periods of its read, switch, and monitor timers. + -See the <> section below. +See the ``<>'' section below. * For a Linux kernel channel: its output type (man:mmap(2) or man:splice(2)). @@ -610,13 +612,13 @@ provided tracing domain. A channel is always associated to a tracing domain (see the -<> section below). The `java.util.logging` (JUL), -log4j, and Python tracing domains each have a default channel which you -can't configure. +``<>'' section below). The `java.util.logging` +(JUL), log4j, and Python tracing domains each have a default channel +which you can't configure. A channel owns recording event rules. -List the channels of a given tracing session with the +List the channels of a given recording session with the man:lttng-list(1) and man:lttng-status(1) commands. Disable an enabled channel with the man:lttng-disable-channel(1) @@ -716,11 +718,12 @@ + Since LTTng{nbsp}2.8, with this mode, LTTng writes to a given sub-buffer its sequence number within its data stream. With a local, network -streaming, or live tracing session (see the <> section above), a trace reader can use such sequence -numbers to report lost packets. A trace reader can use the saved -discarded sub-buffer (packet) count of the trace to decide whether or -not to perform some analysis even if trace data is known to be missing. +streaming, or live recording session (see the +``<>'' section above), a trace +reader can use such sequence numbers to report lost packets. A trace +reader can use the saved discarded sub-buffer (packet) count of the +trace to decide whether or not to perform some analysis even if trace +data is known to be missing. + With this mode, LTTng doesn't write to the trace the exact number of lost event records in the lost sub-buffers. @@ -738,10 +741,10 @@ command. There are a few ways to decrease your probability of losing event -records. The <> -section below shows how to fine-tune the sub-buffer size and count of a -channel to virtually stop losing event records, though at the cost of -greater memory usage. +records. The ``<>'' section below shows how to fine-tune the sub-buffer size and +count of a channel to virtually stop losing event records, though at the +cost of greater memory usage. [[channel-sub-buf-size-count]] @@ -749,8 +752,8 @@ ~~~~~~~~~~~~~~~~~~~~~~~~~ A channel has one or more ring buffer for each CPU of the target system. -See the <> section above to learn -how many ring buffers of a given channel are dedicated to each CPU +See the ``<>'' section above to +learn how many ring buffers of a given channel are dedicated to each CPU depending on its buffering scheme. Set the size of each sub-buffer the ring buffers of a channel contain @@ -772,12 +775,12 @@ event records. + Having larger sub-buffers also ensures a lower sub-buffer switching -frequency (see the <> section below). +frequency (see the ``<>'' section below). + The sub-buffer count is only meaningful if you create the channel in -overwrite mode (see the <> -section above): in this case, if LTTng overwrites a sub-buffer, then the -other sub-buffers are left unaltered. +overwrite mode (see the ``<>'' section above): in this case, if LTTng overwrites a sub-buffer, +then the other sub-buffers are left unaltered. Low event throughput:: In general, prefer smaller sub-buffers since the risk of losing @@ -843,15 +846,15 @@ [IMPORTANT] ==== Even if you don't limit the trace file count, always assume that LTTng -manages all the trace files of the tracing session. +manages all the trace files of the recording session. In other words, there's no safe way to know if LTTng still holds a given trace file open with the trace file rotation feature. The only way to obtain an unmanaged, self-contained LTTng trace before -you destroy the tracing session is with the tracing session rotation -feature (see the <> section above), -which is available since LTTng{nbsp}2.11. +you destroy the recording session is with the recording session rotation +feature (see the ``<>'' section +above), which is available since LTTng{nbsp}2.11. ==== @@ -871,9 +874,9 @@ periodically in case of a low event throughput. + Such a timer is also convenient when you use large sub-buffers (see the -<> section above) -to cope with a sporadic high event throughput, even if the throughput is -otherwise low. +``<>'' section +above) to cope with a sporadic high event throughput, even if the +throughput is otherwise low. + Set the period of the switch timer of a channel, or disable the timer altogether, with the nloption:--switch-timer option of the @@ -898,7 +901,7 @@ statistics to evaluate the following trigger conditions: + -- -. The consumed buffer size of a given tracing session becomes greater +. The consumed buffer size of a given recording session becomes greater than some value. . The buffer usage of a given channel becomes greater than some value. . The buffer usage of a given channel becomes less than some value. @@ -907,7 +910,7 @@ If you disable the monitor timer of a channel{nbsp}__C__: + -- -* The consumed buffer size value of the tracing session of{nbsp}__C__ +* The consumed buffer size value of the recording session of{nbsp}__C__ could be wrong for trigger condition type{nbsp}1: the consumed buffer size of{nbsp}__C__ won't be part of the grand total. @@ -915,7 +918,8 @@ for{nbsp}__C__ will never be satisfied. -- + -See the <> section above to learn more about triggers. +See the ``<>'' section above to learn more about +triggers. + Set the period of the monitor timer of a channel, or disable the timer altogether, with the nloption:--monitor-timer option of the @@ -926,8 +930,9 @@ {sect-recording-event-rule} --------------------------- A _recording event rule_ is a specific type of event rule (see the -<<"event-rule","{sect-event-rule}">> section above) of which the action is -to serialize and record the matched event as an _event record_. +``<<"event-rule","{sect-event-rule}">>'' section above) of which the +action is to serialize and record the matched event as an _event +record_. Set the explicit conditions of a recording event rule when you create it with the man:lttng-enable-event(1) command. A recording event rule also @@ -941,18 +946,18 @@ + A channel is enabled on creation. + -See the <> section above. +See the ``<>'' section above. -* The tracing session of the recording event rule is active (started). +* The recording session of the recording event rule is active (started). + -A tracing session is inactive (stopped) on creation. +A recording session is inactive (stopped) on creation. + -See the <> section above. +See the ``<>'' section above. * The process for which LTTng creates an event to match is allowed to record events. + -All processes are allowed to record events on tracing session +All processes are allowed to record events on recording session creation. + Use the man:lttng-track(1) and man:lttng-untrack(1) commands to select @@ -960,7 +965,7 @@ attributes. You always attach a recording event rule to a channel, which belongs to -a tracing session, when you create it. +a recording session, when you create it. When a recording event rule{nbsp}__ER__ matches an event{nbsp}__E__, LTTng attempts to serialize and record{nbsp}__E__ to one of the @@ -977,7 +982,7 @@ $ lttng enable-event --userspace hello:world --loglevel=INFO ---- -List the recording event rules of a specific tracing session +List the recording event rules of a specific recording session and/or channel with the man:lttng-list(1) and man:lttng-status(1) commands. @@ -985,7 +990,7 @@ command. As of LTTng{nbsp}{lttng_version}, you cannot remove a recording event -rule: it exists as long as its tracing session exists. +rule: it exists as long as its recording session exists. include::common-footer.txt[] diff -Nru ltt-control-2.13~pre/doc/man/lttng-crash.1.txt ltt-control-2.13~pre/doc/man/lttng-crash.1.txt --- ltt-control-2.13~pre/doc/man/lttng-crash.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-crash.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,6 +1,6 @@ lttng-crash(1) ============== -:revdate: 3 May 2021 +:revdate: 14 June 2021 NAME @@ -34,7 +34,7 @@ 'SHMDIR' is the directory specified as the argument of the nloption:--shm-path option of the man:lttng-create(1) command used to -create the tracing session for which to recover the traces. +create the recording session for which to recover the traces. OPTIONS diff -Nru ltt-control-2.13~pre/doc/man/lttng-create.1.txt ltt-control-2.13~pre/doc/man/lttng-create.1.txt --- ltt-control-2.13~pre/doc/man/lttng-create.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-create.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,35 +1,35 @@ lttng-create(1) =============== -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME ---- -lttng-create - Create an LTTng tracing session +lttng-create - Create an LTTng recording session SYNOPSIS -------- -Create a local mode tracing session: +Create a local mode recording session: [verse] *lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *create* ['SESSION'] [option:--shm-path='DIR'] [option:--no-output | option:--output='DIR' | option:--set-url=**file://**__DIR__] -Create a network streaming mode tracing session: +Create a network streaming mode recording session: [verse] *lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *create* ['SESSION'] [option:--shm-path='DIR'] (option:--set-url='URL' | option:--ctrl-url='URL' option:--data-url='URL') -Create a snapshot mode tracing session: +Create a snapshot mode recording session: [verse] *lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *create* ['SESSION'] option:--snapshot [option:--shm-path='DIR'] [option:--no-output | option:--output='DIR' | option:--set-url='URL' | option:--ctrl-url='URL' option:--data-url='URL'] -Create a live mode tracing session: +Create a live mode recording session: [verse] *lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *create* ['SESSION'] option:--live[='DELAYUS'] @@ -37,14 +37,14 @@ DESCRIPTION ----------- -The `lttng create` command creates a new tracing session for your Unix +The `lttng create` command creates a new recording session for your Unix user within the connected session daemon (see the ``Session daemon connection'' section of man:lttng(1) to learn how a user application connects to a session daemon). -See man:lttng-concepts(7) to learn more about tracing sessions. +See man:lttng-concepts(7) to learn more about recording sessions. -Without the 'SESSION' argument, LTTng automatically generates a tracing +Without the 'SESSION' argument, LTTng automatically generates a recording session name having the ++auto-++__YYYYmmdd__++-++__HHMMSS__ form, where 'YYYYmmdd' and 'HHMMSS' are the creation date and time. 'SESSION' may :not: contain the character `/`. @@ -88,37 +88,37 @@ Override the path of the relay daemon binary to spawn with the general genoption:--relayd-path option. -On success, the `create` command sets the current tracing session (see -man:lttng-concepts(7) to learn more) to the created tracing session. +On success, the `create` command sets the current recording session (see +man:lttng-concepts(7) to learn more) to the created recording session. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. -Show the status of the current tracing session with the +Show the status of the current recording session with the man:lttng-status(1) command. -List the tracing sessions of your Unix user, or of all users if +List the recording sessions of your Unix user, or of all users if your Unix user is `root`, within the connected session daemon with the man:lttng-list(1) command. -Start and stop a tracing session with the man:lttng-start(1) and +Start and stop a recording session with the man:lttng-start(1) and man:lttng-stop(1) commands. -Save and load a tracing session with the man:lttng-save(1) and +Save and load a recording session with the man:lttng-save(1) and man:lttng-load(1) commands. Allow and disallow specific processes to record events with the man:lttng-track(1) and man:lttng-untrack(1) commands. -Archive the current trace chunk of (rotate) a tracing session with the +Archive the current trace chunk of (rotate) a recording session with the man:lttng-rotate(1) command. -Destroy a tracing session with the man:lttng-destroy(1) command. +Destroy a recording session with the man:lttng-destroy(1) command. [[modes]] -Tracing session modes -~~~~~~~~~~~~~~~~~~~~~ -As documented in man:lttng-concepts(7), LTTng offers four tracing +Recording session modes +~~~~~~~~~~~~~~~~~~~~~~~ +As documented in man:lttng-concepts(7), LTTng offers four recording session modes: [[local-mode]]Local mode:: @@ -135,7 +135,7 @@ Otherwise::: A subdirectory, under the `$LTTNG_HOME/lttng-traces` (`$LTTNG_HOME` defaults to `$HOME`) directory, of which the name contains the - tracing session name and the date/time. + recording session name and the date/time. [[network-streaming-mode]]Network streaming mode:: Send the trace data over the network to a listening relay daemon @@ -143,7 +143,7 @@ + Set the trace output destination with the option:--set-url option, or with the option:--ctrl-url and option:--data-url options (see the -<> section below). +``<>'' section below). [[snapshot-mode]]Snapshot mode (option:--snapshot option):: Only write the trace data to the local file system or send it to a @@ -153,20 +153,20 @@ With this mode, LTTng: + With the option:--no-output option::: - Does :not: add any snapshot output to the created tracing + Does :not: add any snapshot output to the created recording session. With the option:--output option, the option:--set-url option, or the option:--ctrl-url and option:--data-url options::: Adds a snapshot output named `snapshot-1` using the provided - path or URL(s) to the created tracing session. + path or URL(s) to the created recording session. Otherwise::: Adds an automatic snapshot output named `snapshot-1` to the created - tracing session. + recording session. + The automatic snapshot output is a subdirectory, under the `$LTTNG_HOME/lttng-traces` (`$LTTNG_HOME` defaults to `$HOME`) -directory, of which the name contains the tracing session name and the +directory, of which the name contains the recording session name and the date/time. [[live-mode]]Live mode (option:--live option):: @@ -175,8 +175,8 @@ + Set the trace output destination with the option:--set-url='URL' option, or with the option:--ctrl-url='URL' and option:--data-url='URL' options -(see the <> section below). 'URL' may :not: start -with `file://`. +(see the ``<>'' section below). 'URL' may :not: +start with `file://`. [[url-format]] @@ -194,9 +194,9 @@ {nbsp} + The `file://` protocol targets the *local file system*: you may only use -such an URL with the option:--set-url option when you create the tracing -session in local or snapshot mode (see the <> section above). +such an URL with the option:--set-url option when you create the +recording session in local or snapshot mode (see the ``<>'' section above). + 'TRACEDIR'::: Absolute path to the directory containing the trace data on the @@ -208,9 +208,9 @@ 'NETPROTO'://('HOST' | 'IPADDR')[:__CTRLPORT__[:__DATAPORT__]][/'TRACEDIR'] {nbsp} + -This format is only available when you create the tracing session in +This format is only available when you create the recording session in network streaming, snapshot (option:--snapshot), or live (option:--live) -mode (see the <> section above). +mode (see the ``<>'' section above). + 'NETPROTO'::: Network protocol, amongst: @@ -268,12 +268,12 @@ Mode selection ~~~~~~~~~~~~~~ -See the <> section above. +See the ``<>'' section above. At most one of: option:--live[='DELAYUS']:: - Create the tracing session in live mode. + Create the recording session in live mode. + The optional 'DELAYUS' argument is the maximum time (in µs) you can wait for the data to be flushed (sent to the connected LTTng relay daemon). @@ -287,7 +287,7 @@ (see man:lttng-relayd(8)). option:--snapshot:: - Create the tracing session in snapshot mode. + Create the recording session in snapshot mode. + This is equivalent to: + @@ -295,24 +295,24 @@ + -- With the option:--no-output option:: - Not adding any snapshot output after LTTng creates the tracing + Not adding any snapshot output after LTTng creates the recording session. With the option:--output option, the option:--set-url option, or the option:--ctrl-url and option:--data-url options:: Adding a snapshot output named `snapshot-1` using the provided path - or URL(s) immediately after LTTng creates the tracing session. + or URL(s) immediately after LTTng creates the recording session. Otherwise:: Adding an automatic snapshot output named `snapshot-1` immediately - after LTTng creates the tracing session. + after LTTng creates the recording session. + The automatic snapshot output is a subdirectory, under the `$LTTNG_HOME/lttng-traces` (`$LTTNG_HOME` defaults to `$HOME`) -directory, of which the name contains the tracing session name and the +directory, of which the name contains the recording session name and the date/time. -- -* Forcing all the channels to be created for the tracing session to be +* Forcing all the channels to be created for the recording session to be configured with the nloption:--override and nloption:--output=++mmap++ options (see man:lttng-enable-channel(1)). @@ -320,14 +320,14 @@ Output ~~~~~~ option:--no-output:: - Depending on the tracing session mode (see the <> section above): + Depending on the recording session mode (see the ``<>'' section above): + Local mode::: Disable the file system output. Snapshot mode (option:--snapshot option)::: - Do :not: add a snapshot output after creating the tracing session. + Do :not: add a snapshot output after creating the recording session. option:-o 'DIR', option:--output='DIR':: Equivalent to option:--set-url=++file://++__DIR__. @@ -339,40 +339,40 @@ URL ~~~ -See the <> section above to learn more about the -syntax of the 'URL' argument of the following options. +See the ``<>'' section above to learn more about +the syntax of the 'URL' argument of the following options. option:-C 'URL', option:--ctrl-url='URL':: Set the control path URL to 'URL'. + You must also use the option:--data-url option. + -Not available in local mode (see the <> -section above). +Not available in local mode (see the ``<>'' section above). + In snapshot mode, this is equivalent to using the nloption:--ctrl-url option of the `add-output` action of the man:lttng-snapshot(1) command -immediately after creating the tracing session. +immediately after creating the recording session. option:-D 'URL', option:--data-url='URL':: Set the trace data path URL to 'URL'. + You must also use the option:--ctrl-url option. + -Not available in local mode (see the <> -section above). +Not available in local mode (see the ``<>'' section above). + In snapshot mode, this is equivalent to using the nloption:--data-url option of the `add-output` action of the man:lttng-snapshot(1) command -immediately after creating the tracing session. +immediately after creating the recording session. option:-U 'URL', option:--set-url='URL':: Set the destination URL of the control path and trace data to 'URL'. + -This URL remains unchanged as long as the tracing session exists. +This URL remains unchanged as long as the recording session exists. + -Depending on the tracing session mode (see the <> section above): +Depending on the recording session mode (see the ``<>'' section above): + Local mode::: 'URL' must start with `file://`, followed with the destination @@ -385,7 +385,7 @@ Snapshot mode (option:--snapshot option)::: Equivalent to using the 'URL' non-option argument of the `add-output` action of the man:lttng-snapshot(1) command immediately - after creating the tracing session. + after creating the recording session. include::common-lttng-cmd-help-options.txt[] @@ -397,7 +397,7 @@ [[examples]] EXAMPLES -------- -.Create a normal mode tracing session with a generated name. +.Create a normal mode recording session with a generated name. ==== [role="term"] ---- @@ -405,7 +405,7 @@ ---- ==== -.Create a normal mode tracing session with a custom name. +.Create a normal mode recording session with a custom name. ==== [role="term"] ---- @@ -413,7 +413,7 @@ ---- ==== -.Create a normal mode tracing session with a specific output directory. +.Create a normal mode recording session with a specific output directory. ==== See the option:--output option. @@ -423,7 +423,7 @@ ---- ==== -.Create a network streaming mode tracing session. +.Create a network streaming mode recording session. ==== See the ``Output directory'' section of man:lttng-relayd(8) to understand where the relay daemon to connect to (`10.0.0.242`) writes @@ -437,7 +437,7 @@ ---- ==== -.Create a snapshot mode tracing session with a default snapshot output. +.Create a snapshot mode recording session with a default snapshot output. ==== See the option:--snapshot option. @@ -447,7 +447,7 @@ ---- ==== -.Create a snapshot mode tracing session with a custom snapshot output. +.Create a snapshot mode recording session with a custom snapshot output. ==== See the option:--snapshot and option:--set-url options. @@ -458,7 +458,7 @@ ---- ==== -.Create a snapshot mode tracing session with no snapshot output. +.Create a snapshot mode recording session with no snapshot output. ==== See the option:--snapshot and option:--no-output options. @@ -468,7 +468,7 @@ ---- ==== -.Create an LTTng live mode tracing session with a default relay daemon URL. +.Create an LTTng live mode recording session with a default relay daemon URL. ==== See the option:--live option. @@ -478,7 +478,7 @@ ---- ==== -.Create an LTTng live mode tracing session with a custom live timer period and relay daemon URL. +.Create an LTTng live mode recording session with a custom live timer period and relay daemon URL. ==== See the option:--live and option:--set-url options. @@ -489,7 +489,7 @@ ---- ==== -.Create a normal mode tracing session with a custom directory containing the ring buffer shared memory files. +.Create a normal mode recording session with a custom directory containing the ring buffer shared memory files. ==== See the option:--shm-path option. diff -Nru ltt-control-2.13~pre/doc/man/lttng-destroy.1.txt ltt-control-2.13~pre/doc/man/lttng-destroy.1.txt --- ltt-control-2.13~pre/doc/man/lttng-destroy.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-destroy.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,11 +1,11 @@ lttng-destroy(1) ================ -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME ---- -lttng-destroy - Destroy LTTng tracing sessions +lttng-destroy - Destroy LTTng recording sessions SYNOPSIS @@ -19,65 +19,65 @@ The `lttng destroy` command destroys: With the 'SESSION' argument:: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. With the option:--all option:: - *All* the tracing sessions of the connected session daemon for your - Unix user, or for all users if your Unix user is `root`, as listed - in the output of `lttng list` (see man:lttng-list(1)). + *All* the recording sessions of the connected session daemon for + your Unix user, or for all users if your Unix user is `root`, as + listed in the output of `lttng list` (see man:lttng-list(1)). + See the ``Session daemon connection'' section of man:lttng(1) to learn how a user application connects to a session daemon. Otherwise:: - The current tracing session (see man:lttng-concepts(7) to learn more - about the current tracing session). + The current recording session (see man:lttng-concepts(7) to learn + more about the current recording session). + -In that case, the current tracing session becomes nonexistent. +In that case, the current recording session becomes nonexistent. -See man:lttng-concepts(7) to learn more about tracing sessions. +See man:lttng-concepts(7) to learn more about recording sessions. -``Destroying'' a tracing session means freeing the resources which the +``Destroying'' a recording session means freeing the resources which the LTTng daemons and tracers acquired for it, also making sure to flush all the recorded trace data to either the local file system or the connected -LTTng relay daemon (see man:lttng-relayd(8)), depending on the tracing +LTTng relay daemon (see man:lttng-relayd(8)), depending on the recording session mode. -The `destroy` command stops any tracing activity within the selected -tracing session(s). By default, the command runs an implicit -man:lttng-stop(1) command to ensure that the trace data of the tracing +The `destroy` command stops any recording activity within the selected +recording session(s). By default, the command runs an implicit +man:lttng-stop(1) command to ensure that the trace data of the recording session(s) is valid before it exits. Make the command exit immediately with the option:--no-wait option. In this case, however, the traces(s) might not be valid when the command exits, and there's no way to know when it/they become valid. -If, for a tracing session{nbsp}__TS__ to destroy with the `destroy` +If, for a recording session{nbsp}__RS__ to destroy with the `destroy` command, the following statements are true: * You don't specify the option:--no-wait option. * LTTng archived the current trace chunk (see man:lttng-concepts(7)) - of{nbsp}__TS__ at least once during its lifetime. + of{nbsp}__RS__ at least once during its lifetime. -Then all the subdirectories of the output directory of{nbsp}__TS__ +Then all the subdirectories of the output directory of{nbsp}__RS__ (local or remote) are considered trace chunk archives once the `destroy` command exits. In other words, it's safe to read them, modify them, move them, or remove then. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. include::common-lttng-cmd-options-head.txt[] option:-a, option:--all:: - Destroy all the tracing sessions of your Unix user, or of all users - if your Unix user is `root`, as listed in the output of - man:lttng-list(1), instead of the current tracing session or the - tracing session named 'SESSION'. + Destroy all the recording sessions of your Unix user, or of all + users if your Unix user is `root`, as listed in the output of + man:lttng-list(1), instead of the current recording session or the + recording session named 'SESSION'. option:-n, option:--no-wait:: - Do :not: ensure that the trace data of the tracing session(s) to + Do :not: ensure that the trace data of the recording session(s) to destroy is valid before exiting. @@ -90,7 +90,7 @@ [[examples]] EXAMPLES -------- -.Destroy the current tracing session. +.Destroy the current recording session. ==== [role="term"] ---- @@ -98,7 +98,7 @@ ---- ==== -.Destroy the current tracing session without waiting for completion. +.Destroy the current recording session without waiting for completion. ==== See the option:--no-wait option. @@ -108,7 +108,7 @@ ---- ==== -.Destroy a specific tracing session. +.Destroy a specific recording session. ==== [role="term"] ---- @@ -116,7 +116,7 @@ ---- ==== -.Destroy all tracing sessions. +.Destroy all recording sessions. ==== See the option:--all option. diff -Nru ltt-control-2.13~pre/doc/man/lttng-disable-channel.1.txt ltt-control-2.13~pre/doc/man/lttng-disable-channel.1.txt --- ltt-control-2.13~pre/doc/man/lttng-disable-channel.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-disable-channel.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,6 +1,7 @@ lttng-disable-channel(1) ======================== -:revdate: 17 May 2021 +:revdate: 14 June 2021 + NAME ---- @@ -21,11 +22,11 @@ which belong to: With the option:--session='SESSION' option:: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. Without the option:--session option:: - The current tracing session (see man:lttng-concepts(7) to learn more - about the current tracing session). + The current recording session (see man:lttng-concepts(7) to learn + more about the current recording session). See man:lttng-concepts(7) to learn more about channels. @@ -33,10 +34,10 @@ argument. As of LTTng{nbsp}{lttng_version}, you may :not: enable a disabled -channel once its tracing session has been started (see +channel once its recording session has been started (see man:lttng-start(1)) at least once. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. include::common-lttng-cmd-options-head.txt[] @@ -56,8 +57,8 @@ Recording target ~~~~~~~~~~~~~~~~ option:-s 'SESSION', option:--session='SESSION':: - Disable one or more channels of the tracing session named 'SESSION' - instead of the current tracing session. + Disable one or more channels of the recording session named + 'SESSION' instead of the current recording session. include::common-lttng-cmd-help-options.txt[] @@ -69,7 +70,7 @@ [[examples]] EXAMPLES -------- -.Disable one Linux kernel channel of the current tracing session. +.Disable one Linux kernel channel of the current recording session. ==== [role="term"] ---- @@ -77,7 +78,7 @@ ---- ==== -.Disable two user space channels of a specific tracing session. +.Disable two user space channels of a specific recording session. ==== See the option:--session option. diff -Nru ltt-control-2.13~pre/doc/man/lttng-disable-event.1.txt ltt-control-2.13~pre/doc/man/lttng-disable-event.1.txt --- ltt-control-2.13~pre/doc/man/lttng-disable-event.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-disable-event.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,6 +1,6 @@ lttng-disable-event(1) ====================== -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME @@ -36,11 +36,11 @@ command which belong to: With the option:--session='SESSION' option:: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. Without the option:--session option:: - The current tracing session (see man:lttng-concepts(7) to learn more - about the current tracing session). + The current recording session (see man:lttng-concepts(7) to learn + more about the current recording session). With the option:--channel='CHANNEL' option:: The channel named 'CHANNEL'. @@ -48,7 +48,7 @@ Without the option:--channel option:: The channel named `channel0`. + -If there's more than one channel for the selected tracing session and +If there's more than one channel for the selected recording session and domain, the `disable-event` command fails. See man:lttng-concepts(7) to learn more about recording event rules. @@ -64,7 +64,7 @@ kernel recording event rules regardless of their instrumentation point type. -List the recording event rules of a given tracing session +List the recording event rules of a given recording session and/or channel with the man:lttng-list(1) command. Without the option:--all-events option, the `disable-event` command @@ -74,10 +74,10 @@ man:lttng-list(1)). You may disable an enabled recording event rule regardless of the -activity (started or stopped) of its tracing session (see +activity (started or stopped) of its recording session (see man:lttng-start(1) and man:lttng-stop(1)). -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. include::common-lttng-cmd-options-head.txt[] @@ -111,8 +111,8 @@ 'CHANNEL' instead of `channel0`. option:-s 'SESSION', option:--session='SESSION':: - Disable recording event rules in the tracing session named 'SESSION' - instead of the current tracing session. + Disable recording event rules in the recording session named + 'SESSION' instead of the current recording session. Instrumentation point type condition @@ -163,7 +163,7 @@ [[examples]] EXAMPLES -------- -.Disable all Linux kernel tracepoint recording event rules in the default channel of the current tracing session. +.Disable all Linux kernel tracepoint recording event rules in the default channel of the current recording session. ==== See the option:--all-events option. @@ -173,7 +173,7 @@ ---- ==== -.Disable specific Apache log4j recording event rules in the default channel of a specific tracing session. +.Disable specific Apache log4j recording event rules in the default channel of a specific recording session. ==== See the option:--session option. @@ -184,7 +184,7 @@ ---- ==== -.Disable all user space recording event rules in a specific channel of the current tracing session. +.Disable all user space recording event rules in a specific channel of the current recording session. ==== See the option:--channel option. @@ -195,7 +195,7 @@ ---- ==== -.Disable specific Linux kernel system call recording event rules in the default channel of the current tracing session. +.Disable specific Linux kernel system call recording event rules in the default channel of the current recording session. ==== [role="term"] ---- diff -Nru ltt-control-2.13~pre/doc/man/lttng-disable-rotation.1.txt ltt-control-2.13~pre/doc/man/lttng-disable-rotation.1.txt --- ltt-control-2.13~pre/doc/man/lttng-disable-rotation.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-disable-rotation.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,11 +1,11 @@ lttng-disable-rotation(1) ========================= -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME ---- -lttng-disable-rotation - Unset an LTTng tracing session rotation schedule +lttng-disable-rotation - Unset an LTTng recording session rotation schedule SYNOPSIS @@ -21,16 +21,16 @@ previously set with the man:lttng-enable-rotation(1) command, for: With the option:--session='SESSION' option:: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. Without the option:--session option:: - The current tracing session (see man:lttng-concepts(7) to learn more - about the current tracing session). + The current recording session (see man:lttng-concepts(7) to learn + more about the current recording session). -See man:lttng-concepts(7) to learn more about the tracing session +See man:lttng-concepts(7) to learn more about the recording session rotation and trace chunk concepts. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. include::common-lttng-cmd-options-head.txt[] @@ -50,8 +50,8 @@ Recording target ~~~~~~~~~~~~~~~~ option:-s 'SESSION', option:--session='SESSION':: - Unset a rotation schedule for the tracing session named 'SESSION' - instead of the current tracing session. + Unset a rotation schedule for the recording session named 'SESSION' + instead of the current recording session. include::common-lttng-cmd-help-options.txt[] @@ -63,7 +63,7 @@ [[examples]] EXAMPLES -------- -.Unset the size-based rotation schedule of the current tracing session. +.Unset the size-based rotation schedule of the current recording session. ==== See the option:--size option. @@ -73,7 +73,7 @@ ---- ==== -.Unset the periodic rotation schedule of a specific tracing session. +.Unset the periodic rotation schedule of a specific recording session. ==== See the option:--timer and option:--session options. diff -Nru ltt-control-2.13~pre/doc/man/lttng-enable-channel.1.txt ltt-control-2.13~pre/doc/man/lttng-enable-channel.1.txt --- ltt-control-2.13~pre/doc/man/lttng-enable-channel.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-enable-channel.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,6 +1,6 @@ lttng-enable-channel(1) ======================= -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME @@ -54,18 +54,18 @@ The channel(s) to create or enable belong to: With the option:--session='SESSION' option:: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. Without the option:--session option:: - The current tracing session (see man:lttng-concepts(7) to learn more - about the current tracing session). + The current recording session (see man:lttng-concepts(7) to learn + more about the current recording session). NOTE: The man:lttng-enable-event(1) command can automatically create a default channel when no channel exists for the provided tracing domain. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. -List the channels of a given tracing session with the +List the channels of a given recording session with the man:lttng-list(1) and man:lttng-status(1) commands. Disable an enabled channel with the man:lttng-disable-channel(1) @@ -78,16 +78,16 @@ * Change an attribute of an existing channel. -* Enable a disabled channel once its tracing session has been active +* Enable a disabled channel once its recording session has been active (started; see man:lttng-start(1)) at least once. -* Create a channel once its tracing session has been active at least +* Create a channel once its recording session has been active at least once. * Create a user space channel with a given buffering scheme (option:--buffers-uid or option:--buffers-pid options) and create a second user space channel with a different buffering scheme in the - same tracing session. + same recording session. ==== @@ -108,8 +108,8 @@ Recording target ~~~~~~~~~~~~~~~~ option:-s 'SESSION', option:--session='SESSION':: - Create or enable channels in the tracing session named 'SESSION' - instead of the current tracing session. + Create or enable channels in the recording session named 'SESSION' + instead of the current recording session. Buffering scheme @@ -356,10 +356,10 @@ [[examples]] EXAMPLES -------- -.Create a Linux kernel channel with default attributes in the current tracing session. +.Create a Linux kernel channel with default attributes in the current recording session. ==== The following command line only creates a new channel if `my-channel` -doesn't name an existing Linux kernel channel in the current tracing +doesn't name an existing Linux kernel channel in the current recording session. [role="term"] @@ -368,7 +368,7 @@ ---- ==== -.Create a user space channel with a per-process buffering scheme in a specific tracing session. +.Create a user space channel with a per-process buffering scheme in a specific recording session. ==== See the option:--session and option:--buffers-pid options. @@ -379,7 +379,7 @@ ---- ==== -.Create a Linux kernel channel in the current tracing session with four 32-MiB sub-buffers per ring buffer. +.Create a Linux kernel channel in the current recording session with four 32-MiB sub-buffers per ring buffer. ==== See the option:--num-subbuf and option:--subbuf-size options. @@ -390,7 +390,7 @@ ---- ==== -.Create a user space channel in the current tracing session with trace file rotation. +.Create a user space channel in the current recording session with trace file rotation. ==== See the option:--tracefile-count and option:--tracefile-size options. @@ -401,7 +401,7 @@ ---- ==== -.Enable two user space channels of a specific tracing session. +.Enable two user space channels of a specific recording session. ==== [role="term"] ---- diff -Nru ltt-control-2.13~pre/doc/man/lttng-enable-event.1.txt ltt-control-2.13~pre/doc/man/lttng-enable-event.1.txt --- ltt-control-2.13~pre/doc/man/lttng-enable-event.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-enable-event.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,6 +1,6 @@ lttng-enable-event(1) ===================== -:revdate: 25 May 2021 +:revdate: 14 June 2021 NAME @@ -52,7 +52,7 @@ * Enable one or more disabled recording event rules. + -See the <> section +See the ``<>'' section below. See man:lttng-concepts(7) to learn more about instrumentation points, @@ -61,11 +61,11 @@ The recording event rule(s) to create or enable belong to: With the option:--session='SESSION' option:: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. Without the option:--session option:: - The current tracing session (see man:lttng-concepts(7) to learn more - about the current tracing session). + The current recording session (see man:lttng-concepts(7) to learn + more about the current recording session). With the option:--channel='CHANNEL' option:: The channel named 'CHANNEL'. @@ -73,13 +73,13 @@ Without the option:--channel option:: The channel named `channel0`. + -If there's already a channel for the selected tracing session and domain -which isn't named `channel0`, the `enable-event` command fails. +If there's already a channel for the selected recording session and +domain which isn't named `channel0`, the `enable-event` command fails. Otherwise, it automatically creates it. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. -List the recording event rules of a specific tracing session +List the recording event rules of a specific recording session and/or channel with the man:lttng-list(1) and man:lttng-status(1) commands. @@ -101,25 +101,25 @@ * The instrumentation point type from which LTTng creates{nbsp}__E__ has a specific type. + -See the <> -section below. +See the ``<>'' section below. * A pattern matches the name of{nbsp}__E__ while another pattern doesn't. + -See the <> section below. +See the ``<>'' section below. * The log level of the instrumentation point from which LTTng creates{nbsp}__E__ is at least as severe as some value, or is exactly some value. + -See the <> -section below. +See the ``<>'' section below. * The fields of the payload of{nbsp}__E__ and the current context fields satisfy a filter expression. + -See the <> +See the ``<>'' section below. -- @@ -138,16 +138,16 @@ + Enable a disabled channel with the man:lttng-enable-channel(1) command. -* The tracing session of{nbsp}__ER__ is active (started). +* The recording session of{nbsp}__ER__ is active (started). + -A tracing session is inactive (stopped) on creation. +A recording session is inactive (stopped) on creation. + -Start an inactive tracing session with the man:lttng-start(1) command. +Start an inactive recording session with the man:lttng-start(1) command. * The process for which LTTng creates{nbsp}__E__ is allowed to record events. + -All processes are allowed to record events on tracing session +All processes are allowed to record events on recording session creation. + Use the man:lttng-track(1) and man:lttng-untrack(1) commands to select @@ -193,7 +193,7 @@ The argument of the option:--probe option is the location of the kprobe to insert, either a symbol or a memory address, while 'RECORDNAME' is the name of the record -of{nbsp}__E__ (see the <> section below). +of{nbsp}__E__ (see the ``<>'' section below). + The payload of a Linux kprobe event is empty. @@ -215,7 +215,7 @@ -- + 'RECORDNAME' is the name of the record of{nbsp}__E__ (see the -<> section below). +``<>'' section below). + The payload of a Linux user space probe event is empty. @@ -226,7 +226,7 @@ The argument of the option:--function option is the location of the Linux kretprobe to insert, either a symbol or a memory address, while 'RECORDNAME' is the name of the record -of{nbsp}__E__ (see the <> section below). +of{nbsp}__E__ (see the ``<>'' section below). + The payload of a Linux kretprobe event is empty. @@ -264,8 +264,8 @@ * You specify the option:--all option or, depending on the instrumentation type condition (see the - <> section - above) of{nbsp}__ER__, 'NAME' matches: + ``<>'' + section above) of{nbsp}__ER__, 'NAME' matches: + -- LTTng tracepoint:: @@ -553,8 +553,8 @@ ~~~~~~~~~~~~~~~~~ When LTTng records an event{nbsp}__E__, the resulting event record has a name which depends on the instrumentation point type condition (see the -<> section -above) of the recording event rule which matched{nbsp}__E__: +``<>'' +section above) of the recording event rule which matched{nbsp}__E__: LTTng tracepoint (option:--kernel/option:--userspace and option:--tracepoint options):: Full name of the tracepoint from which LTTng creates{nbsp}__E__. @@ -612,7 +612,7 @@ as listed in the output of the man:lttng-list(1) command. You may enable a disabled recording event rule regardless of the -activity (started or stopped) of its tracing session (see +activity (started or stopped) of its recording session (see man:lttng-start(1) and man:lttng-stop(1)). To enable a disabled recording event rule, run the `enable-event` @@ -655,14 +655,14 @@ 'CHANNEL' instead of `channel0`. option:-s 'SESSION', option:--session='SESSION':: - Create or enable recording event rules in the tracing session named - 'SESSION' instead of the current tracing session. + Create or enable recording event rules in the recording session + named 'SESSION' instead of the current recording session. Instrumentation point type condition ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -See the <> -section above. +See the ``<>'' section above. At most one of: @@ -681,7 +681,7 @@ -- + You must specify the event record name with 'RECORDNAME'. See the -<> section above to learn more. +``<>'' section above to learn more. option:--probe='LOC':: Only match Linux kprobe events. @@ -697,7 +697,7 @@ -- + You must specify the event record name with 'RECORDNAME'. See the -<> section above to learn more. +``<>'' section above to learn more. option:--userspace-probe='LOC':: Only match Linux user space probe events. @@ -773,7 +773,7 @@ -- + You must specify the event record name with 'RECORDNAME'. See the -<> section above to learn more. +``<>'' section above to learn more. option:--syscall:: Only match Linux system call events. @@ -800,7 +800,7 @@ Event name condition ~~~~~~~~~~~~~~~~~~~~ -See the <> section above. +See the ``<>'' section above. option:-a, option:--all:: Equivalent to a single 'NAME' argument (LTTng tracepoint or logger @@ -821,8 +821,8 @@ Instrumentation point log level condition ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -See the <> section above. +See the ``<>'' section above. At most one of: @@ -840,7 +840,7 @@ Event payload and context filter condition ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -See the <> +See the ``<>'' section above. option:-f 'EXPR', option:--filter='EXPR':: @@ -860,7 +860,7 @@ [[examples]] EXAMPLES -------- -.Create a recording event rule which matches all Linux system call events (current tracing session, default channel). +.Create a recording event rule which matches all Linux system call events (current recording session, default channel). ==== See the option:--all and option:--syscall options. @@ -870,7 +870,7 @@ ---- ==== -.Create a recording event rule which matches user space tracepoint events named specifically (current tracing session, default channel). +.Create a recording event rule which matches user space tracepoint events named specifically (current recording session, default channel). ==== The recording event rule below matches all user space tracepoint events of which the name starts with `my_provider:msg`. @@ -881,7 +881,7 @@ ---- ==== -.Create three recording event rules which match Python logging events named specifically (current tracing session, default channel). +.Create three recording event rules which match Python logging events named specifically (current recording session, default channel). ==== [role="term"] ---- @@ -889,7 +889,7 @@ ---- ==== -.Create a recording event rule which matches Apache log4j logging events with a specific log level range (current tracing session, specific channel). +.Create a recording event rule which matches Apache log4j logging events with a specific log level range (current recording session, specific channel). ==== See the option:--channel, option:--all, and option:--loglevel options. @@ -900,11 +900,11 @@ ---- ==== -.Create a recording event rule which matches specific Linux kprobe events (current tracing session, default channel). +.Create a recording event rule which matches specific Linux kprobe events (current recording session, default channel). ==== The recording event rule below matches the entry of `usb_disconnect()` Linux kernel function calls. The records of such events are named `usbd` -(see the <> section above). +(see the ``<>'' section above). See the option:--probe option. @@ -914,7 +914,7 @@ ---- ==== -.Create a recording event rule which matches Linux kernel tracepoint events which satisfy an event payload and context filter (specific tracing session, default channel). +.Create a recording event rule which matches Linux kernel tracepoint events which satisfy an event payload and context filter (specific recording session, default channel). ==== See the option:--session and option:--filter options. @@ -925,7 +925,7 @@ ---- ==== -.Enable two Linux kernel tracepoint recording event rules (current tracing session, specific channel). +.Enable two Linux kernel tracepoint recording event rules (current recording session, specific channel). ==== See the option:--channel option. diff -Nru ltt-control-2.13~pre/doc/man/lttng-enable-rotation.1.txt ltt-control-2.13~pre/doc/man/lttng-enable-rotation.1.txt --- ltt-control-2.13~pre/doc/man/lttng-enable-rotation.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-enable-rotation.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,11 +1,11 @@ lttng-enable-rotation(1) ======================== -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME ---- -lttng-enable-rotation - Set an LTTng tracing session rotation schedule +lttng-enable-rotation - Set an LTTng recording session rotation schedule SYNOPSIS @@ -17,17 +17,17 @@ DESCRIPTION ----------- -The `lttng enable-rotation` command sets a tracing session rotation +The `lttng enable-rotation` command sets a recording session rotation schedule for: With the option:--session='SESSION' option:: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. Without the option:--session option:: - The current tracing session (see man:lttng-concepts(7) to learn more - about the current tracing session). + The current recording session (see man:lttng-concepts(7) to learn more + about the current recording session). -See man:lttng-concepts(7) to learn more about the tracing session +See man:lttng-concepts(7) to learn more about the recording session rotation and trace chunk concepts. With the option:--timer='PERIODUS' option, the `enable-rotation` command @@ -41,8 +41,8 @@ For both the option:--timer and option:--size options, LTTng checks the schedule condition periodically using the monitor timers of the channels -of the selected tracing session (see the nloption:--monitor-timer option -of the man:lttng-enable-channel(1) command). This means that: +of the selected recording session (see the nloption:--monitor-timer +option of the man:lttng-enable-channel(1) command). This means that: * With the option:--timer='PERIODUS' option, LTTng can perform an automatic rotation when the elapsed time since the last automatic @@ -60,24 +60,24 @@ See the man:lttng-concepts(7) to learn how LTTng names a trace chunk archive directory. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. -Unset a tracing session rotation schedule with the +Unset a recording session rotation schedule with the man:lttng-disable-rotation(1) command. [IMPORTANT] ==== You may only use the `enable-rotation` command when: -* The selected tracing session was created in normal mode or in network - streaming mode (see man:lttng-create(1)). +* The selected recording session was created in normal mode or in + network streaming mode (see man:lttng-create(1)). * No channel was created with a configured trace file count or size limit (see the nloption:--tracefile-size and nloption:--tracefile-count options of the man:lttng-enable-channel(1) command). -For a given tracing session, LTTng only performs an automatic rotation +For a given recording session, LTTng only performs an automatic rotation when it's not currently performing a rotation. ==== @@ -106,8 +106,8 @@ Recording target ~~~~~~~~~~~~~~~~ option:-s 'SESSION', option:--session='SESSION':: - Set a rotation schedule for the tracing session named 'SESSION' - instead of the current tracing session. + Set a rotation schedule for the recording session named 'SESSION' + instead of the current recording session. include::common-lttng-cmd-help-options.txt[] @@ -119,7 +119,7 @@ [[examples]] EXAMPLES -------- -.Set the size-based rotation schedule of the current tracing session. +.Set the size-based rotation schedule of the current recording session. ==== See the option:--size option. @@ -129,7 +129,7 @@ ---- ==== -.Set the periodic rotation schedule of a specific tracing session. +.Set the periodic rotation schedule of a specific recording session. ==== See the option:--timer and option:--session options. diff -Nru ltt-control-2.13~pre/doc/man/lttng-event-rule.7.txt ltt-control-2.13~pre/doc/man/lttng-event-rule.7.txt --- ltt-control-2.13~pre/doc/man/lttng-event-rule.7.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-event-rule.7.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,6 +1,6 @@ lttng-event-rule(7) =================== -:revdate: 12 May 2021 +:revdate: 18 May 2021 NAME @@ -14,26 +14,26 @@ events: [verse] -option:--domain=**kernel** option:--type=(**tracepoint** | **syscall**[**:entry**|**:exit**|**pass:[:entry+exit]**])] +option:--type=(**kernel:tracepoint** | **kernel:syscall**[**:entry**|**:exit**|**pass:[:entry+exit]**])] pass:[[]option:--name='NAME'] [option:--filter='EXPR'] Specify an event rule to match Linux kernel kprobe or user space probe events: [verse] -option:--domain=**kernel** option:--type=(**kprobe** | **uprobe**) option:--location='LOC' +option:--type=(**kernel:kprobe** | **kernel:uprobe**) option:--location='LOC' pass:[[]option:--event-name='EVENTNAME'] Specify an event rule to match user space tracepoint events: [verse] -option:--domain=**user** [option:--type=**tracepoint**] [option:--name='NAME'] [option:--exclude-name='XNAME']... +option:--type=**user:tracepoint** [option:--name='NAME'] [option:--exclude-name='XNAME']... pass:[[]option:--log-level=('LOGLEVEL' | 'LOGLEVEL'.. | ..)] [option:--filter='EXPR'] Specify an event rule to match Java/Python logging events: [verse] -option:--domain=(**jul** | **log4j** | **python**) [option:--type=**logging**] [option:--name='NAME'] +option:--type=(**jul** | **log4j** | **python**)**:logging** [option:--name='NAME'] pass:[[]option:--log-level=('LOGLEVEL' | 'LOGLEVEL'.. | ..)] [option:--filter='EXPR'] @@ -69,25 +69,25 @@ * The instrumentation point from which LTTng creates{nbsp}__E__ has a specific type. + -See the <> -section below. +See the ``<>'' section below. * A pattern matches the name of{nbsp}__E__ while another pattern doesn't. + -See the <> section below. +See the ``<>'' section below. * The log level of the instrumentation point from which LTTng creates{nbsp}__E__ is at least as severe as some value, or is exactly some value. + -See the <> section below. +See the ``<>'' section below. * The fields of the payload of{nbsp}__E__ and the current context fields satisfy a filter expression. + -See the <> +See the ``<>'' section below. The dedicated command-line options of most conditions are optional: if @@ -100,40 +100,38 @@ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ An event{nbsp}__E__ satisfies the instrumentation point type condition of an event rule if the instrumentation point from which LTTng -creates{nbsp}__E__ is: +creates{nbsp}__E__ is, depending on the argument of the option:--type +option: -For the Linux kernel tracing domain (option:--domain=++kernel++ option):: - With the option:--type=++tracepoint++ option or without any option:--type option::: - An LTTng kernel tracepoint, that is, a statically defined point - in the source code of the kernel image or of a kernel module - with LTTng kernel tracer macros. -+ -As of LTTng{nbsp}{lttng_version}, this is the default instrumentation -point type of the Linux kernel tracing domain, but this may change in -the future. +`kernel:tracepoint`:: + An LTTng kernel tracepoint, that is, a statically defined point + in the source code of the kernel image or of a kernel module + with LTTng kernel tracer macros. + List the available Linux kernel tracepoints with `lttng list --kernel`. See man:lttng-list(1) to learn more. - With the option:--type=++syscall++, option:--type=++syscall:entry++, option:--type=++syscall:exit++, or option:--type=++syscall:entry+exit++ option::: - The entry, exit, or entry and exit of a Linux kernel system - call. +`kernel:syscall:entry`:: +`kernel:syscall:exit`:: +`kernel:syscall:entry+exit`:: + The entry, exit, or entry and exit of a Linux kernel system + call. + List the available Linux kernel system call instrumentation points with `lttng list --kernel --syscall`. See man:lttng-list(1) to learn more. - With the option:--type=++kprobe++ option::: - A Linux kprobe, that is, a single probe dynamically placed in - the compiled kernel code. +`kernel:kprobe`:: + A Linux kprobe, that is, a single probe dynamically placed in + the compiled kernel code. + You must specify the kprobe location with the option:--location option. + The payload of a Linux kprobe event is empty. - With the option:--type=++uprobe++ option::: - A Linux user space probe, that is, a single probe dynamically - placed at the entry of a compiled user space application/library - function through the kernel. +`kernel:uprobe`:: + A Linux user space probe, that is, a single probe dynamically + placed at the entry of a compiled user space application/library + function through the kernel. + LTTng{nbsp}{lttng_version} supports the ELF and SystemTap User-level Statically Defined Tracing (USDT; a DTrace-style marker) probing @@ -145,30 +143,31 @@ + The payload of a Linux user space probe event is empty. -For the user space tracing domain (option:--domain=++user++ option):: - With or without the option:--type=++tracepoint++ option::: - An LTTng user space tracepoint, that is, a statically defined point - in the source code of a C/$$C++$$ application/library - with LTTng user space tracer macros. -+ -As of LTTng{nbsp}{lttng_version}, this is the default and sole -instrumentation point type of the user space tracing domain, but this -may change in the future. +`user:tracepoint`:: + An LTTng user space tracepoint, that is, a statically defined point + in the source code of a C/$$C++$$ application/library with LTTng + user space tracer macros. + List the available user space tracepoints with `lttng list --userspace`. See man:lttng-list(1) to learn more. -For the `java.util.logging` (option:--domain=++jul++ option), Apache log4j (option:--domain=++log4j++ option), and Python (option:--domain=++python++ option) tracing domains:: - With or without the option:--type=++logging++ option::: - A logging statement. -+ -As of LTTng{nbsp}{lttng_version}, this is the default and sole -instrumentation point type of the `java.util.logging`, Apache log4j, and -Python tracing domains, but this may change in the future. -+ -List the available Java and Python loggers with `lttng list --jul`, -`lttng list --log4j`, and `lttng list --python`. See man:lttng-list(1) -to learn more. +`jul:logging`:: + A `java.util.logging` logging statement. ++ +List the available `java.util.logging` loggers with `lttng list --jul` +See man:lttng-list(1) to learn more. + +`log4j:logging`:: + An Apache log4j logging statement. ++ +List the available Apache log4j loggers with `lttng list --log4j` +See man:lttng-list(1) to learn more. + +`python:logging`:: + A Python logging statement. ++ +List the available Python loggers with `lttng list --python` See +man:lttng-list(1) to learn more. [[event-name-cond]] @@ -179,22 +178,27 @@ * You don't specify the option:--name='NAME' option or, depending on the instrumentation type condition (see the - <> section - above) of{nbsp}__ER__, 'NAME' matches: + ``<>'' + section above) of{nbsp}__ER__, 'NAME' matches: + -- -LTTng tracepoint:: +`kernel:tracepoint`:: +`user:tracepoint`:: The full name of the tracepoint from which LTTng creates{nbsp}__E__. + Note that the full name of a user space tracepoint is __PROVIDER__++:++__NAME__, where __PROVIDER__ is the tracepoint provider name and __NAME__ is the tracepoint name. -Logging statement:: +`jul:logging`:: +`log4j:logging`:: +`python:logging`:: The name of the Java or Python logger from which LTTng creates{nbsp}__E__. -Linux system call:: +`kernel:syscall:entry`:: +`kernel:syscall:exit`:: +`kernel:syscall:entry+exit`:: The name of the system call, without any `sys_` prefix, from which LTTng creates{nbsp}__E__. -- @@ -204,7 +208,7 @@ tracepoint from which LTTng creates{nbsp}__E__. + The option:--exclude-name option is only available with the -option:--domain=++user++ option. +option:--type=++user:tracepoint++ option. This condition is only meaningful for the LTTng tracepoint, logging statement, and Linux system call instrumentation point types: it's @@ -251,10 +255,10 @@ and logging statement instrumentation point types: it's always satisfied for other types. -The available values of 'LOGLEVEL' are, depending on the tracing domain, -from the most to the least severe: +The available values of 'LOGLEVEL' are, depending on the argument of +the option:--type option, from the most to the least severe: -User space (option:--domain=++user++ option):: +`user:tracepoint`:: + * `EMERG` (0) * `ALERT` (1) @@ -272,7 +276,7 @@ * `DEBUG_LINE` (13) * `DEBUG` (14) -`java.util.logging` (option:--domain=++jul++ option):: +`jul:logging`:: + * `OFF` (`INT32_MAX`) * `SEVERE` (1000) @@ -284,7 +288,7 @@ * `FINEST` (300) * `ALL` (`INT32_MIN`) -Apache log4j (option:--domain=++log4j++ option):: +`log4j:logging`:: + * `OFF` (`INT32_MAX`) * `FATAL` (50000) @@ -295,7 +299,7 @@ * `TRACE` (5000) * `ALL` (`INT32_MIN`) -Python (option:--domain=++python++ option):: +`python:logging`:: + * `CRITICAL` (50) * `ERROR` (40) @@ -472,68 +476,73 @@ |=== |Recording event rule option(s)/argument(s) |Common event rule option(s) -|nloption:--kernel |option:--domain=++kernel++ -|nloption:--userspace |option:--domain=++user++ -|nloption:--jul |option:--domain=++jul++ -|nloption:--log4j |option:--domain=++log4j++ -|nloption:--python |option:--domain=++python++ -|nloption:--tracepoint (with nloption:--kernel/nloption:--userspace) |option:--type=++tracepoint++ or no option:--type option -|nloption:--tracepoint (with nloption:--jul/nloption:--log4j/nloption:--python) |option:--type=++logging++ or no option:--type option -|nloption:--syscall |option:--type=++syscall++ or option:--type=++syscall:entry+exit++ -|nloption:--probe='LOC' and 'RECORDNAME' (non-option) |option:--type=++kprobe++, option:--location='LOC', and option:--event-name='RECORDNAME' -|nloption:--userspace-probe='LOC' and 'RECORDNAME' (non-option) |option:--type=++uprobe++, option:--location='LOC', and option:--event-name='RECORDNAME' -|nloption:--function='LOC' and 'RECORDNAME' (non-option) |Not available as of LTTng{nbsp}{lttng_version} -|'NAME' (non-option) |option:--name='NAME' -|nloption:--all |option:--name=++\'*\'++ or no option:--name option -|nloption:--exclude=__XNAME__[++,++__XNAME__]... |option:--exclude-name='XNAME' for each 'XNAME' -|nloption:--loglevel='LOGLEVEL' |option:--log-level=__LOGLEVEL__++..++ -|nloption:--loglevel-only='LOGLEVEL' |option:--log-level=__LOGLEVEL__ -|nloption:--filter='EXPR' |option:--filter='EXPR' +|nloption:--kernel and nloption:--tracepoint +|option:--type=++kernel:tracepoint++ + +|nloption:--kernel and nloption:--syscall +|option:--type=++kernel:syscall:entry+exit++ + +|nloption:--probe='LOC' and 'RECORDNAME' (non-option) +|option:--type=++kernel:kprobe++, option:--location='LOC', and +option:--event-name='RECORDNAME' + +|nloption:--userspace-probe='LOC' and 'RECORDNAME' (non-option) +|option:--type=++kernel:uprobe++, option:--location='LOC', and +option:--event-name='RECORDNAME' + +|nloption:--function='LOC' and 'RECORDNAME' (non-option) +|Not available as of LTTng{nbsp}{lttng_version} + +|nloption:--userspace and nloption:--tracepoint +|option:--type=++user:tracepoint++ + +|nloption:--jul and nloption:--tracepoint +|option:--type=++jul:logging++ + +|nloption:--log4j and nloption:--tracepoint +|option:--type=++log4j:logging++ + +|nloption:--python and nloption:--tracepoint +|option:--type=++python:logging++ + +|'NAME' (non-option) +|option:--name='NAME' + +|nloption:--all +|option:--name=++\'*\'++ or no option:--name option + +|nloption:--exclude=__XNAME__[++,++__XNAME__]... +|option:--exclude-name='XNAME' for each 'XNAME' + +|nloption:--loglevel='LOGLEVEL' +|option:--log-level=__LOGLEVEL__++..++ + +|nloption:--loglevel-only='LOGLEVEL' +|option:--log-level=__LOGLEVEL__ + +|nloption:--filter='EXPR' +|option:--filter='EXPR' |=== OPTIONS ------- -Tracing domain -~~~~~~~~~~~~~~ -option:-d 'DOMAIN', option:--domain='DOMAIN':: - Only match events which LTTng creates in the tracing domain - 'DOMAIN'. -+ -'DOMAIN' is one of: -+ --- -`kernel`::: - Linux kernel -`user`::: -`userspace`::: - User space tracing -`jul`::: - `java.util.logging` -`log4j`::: - Apache log4j -`python`::: - Python --- -+ -This option is mandatory. - - Instrumentation point type condition ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -See the <> -section above. +See the ``<>'' section above. option:-E 'NAME', option:--event-name='NAME':: - With the option:--type=++kprobe++ or option:--type=++uprobe++ - option, set the name of the emitted events to 'NAME' instead of the - 'LOC' argument of the option:--location='LOC' option. + With the option:--type=++kernel:kprobe++ or + option:--type=++kernel:uprobe++ option, set the name of the emitted + events to 'NAME' instead of the 'LOC' argument of the + option:--location='LOC' option. + Defaulting to 'LOC' is specific to LTTng{nbsp}{lttng_version} and may change in the future. option:-L 'LOC', option:--location='LOC':: - With the option:--type=++kprobe++ option::: + With the option:--type=++kernel:kprobe++ option::: Set the location of the Linux kprobe to insert to 'LOC'. + 'LOC' is one of: @@ -542,7 +551,7 @@ * A symbol name. * A symbol name and an offset (__SYMBOL__++pass:[+]++__OFFSET__ format). - With the option:--type=++uprobe++ option::: + With the option:--type=++kernel:uprobe++ option::: Set the location of the user space probe to insert to 'LOC'. + 'LOC' is one of: @@ -616,53 +625,46 @@ + 'TYPE' is one of: + --- -`tracepoint`:: - LTTng tracepoint. -+ -Only available with the option:--domain=++kernel++ and -option:--domain=++user++ options. -+ -As of LTTng{nbsp}{lttng_version}, this is the default instrumentation -point type of the Linux kernel and user space tracing domains, but this -may change in the future. - -`logging`:: - Logging statement. +`kernel:tracepoint`::: + LTTng kernel tracepoint. + -Only available with the option:--domain=++jul++, -option:--domain=++log4j++, and option:--domain=++python++ options. -+ -As of LTTng{nbsp}{lttng_version}, this is the default instrumentation -point type of the `java.util.logging`, Apache log4j, and Python tracing -domains, but this may change in the future. +As of LTTng{nbsp}{lttng_version}, `kernel` is an alias, but this may +change in the future. -`syscall`:: - As of LTTng{nbsp}{lttng_version}, equivalent to - `syscall:entry+exit`, but this default may change in the future. +`user:tracepoint`::: + LTTng user space tracepoint. + -Only available with the option:--domain=++kernel++ option. +As of LTTng{nbsp}{lttng_version}, `user` is an alias, but this may +change in the future. -`syscall:entry`:: +`kernel:syscall:entry`::: Linux system call entry. + -Only available with the option:--domain=++kernel++ option. +As of LTTng{nbsp}{lttng_version}, `syscall:entry` is an alias, but this +may change in the future. -`syscall:exit`:: +`kernel:syscall:exit`::: Linux system call exit. + -Only available with the option:--domain=++kernel++ option. +As of LTTng{nbsp}{lttng_version}, `syscall:exit` is an alias, but this +may change in the future. -`syscall:entry+exit`:: +`kernel:syscall:entry+exit`::: Linux system call entry and exit (two distinct instrumentation points). + -Only available with the option:--domain=++kernel++ option. +As of LTTng{nbsp}{lttng_version}, the following are aliases, but this +may change in the future: ++ +* `syscall:entry+exit` +* `kernel:syscall` +* `syscall` -`kprobe`:: +`kernel:kprobe`::: Linux kprobe. + -Only available with the option:--domain=++kernel++ option. +As of LTTng{nbsp}{lttng_version}, `kprobe` is an alias, but this may +change in the future. + You must specify the location of the kprobe to insert with the option:--location option. @@ -670,39 +672,59 @@ You may specify the name of the emitted events with the option:--event-name option. -`uprobe` or `userspace-probe`:: +`kernel:uprobe`::: Linux user space probe. + -Only available with the option:--domain=++kernel++ option. -+ You must specify the location of the user space probe to insert with the option:--location option. + You may specify the name of the emitted events with the option:--event-name option. --- + +`jul:logging`::: + `java.util.logging` logging statement. ++ +As of LTTng{nbsp}{lttng_version}, `jul` is an alias, but this may change +in the future. + +`log4j:logging`::: + Apache log4j logging statement. ++ +As of LTTng{nbsp}{lttng_version}, `log4j` is an alias, but this may +change in the future. + +`python:logging`::: + Python logging statement. ++ +As of LTTng{nbsp}{lttng_version}, `python` is an alias, but this may +change in the future. Event name condition ~~~~~~~~~~~~~~~~~~~~ -See the <> section above. +See the ``<>'' section above. option:-n 'NAME', option:--name='NAME':: - Only match events of which 'NAME' matches: + Only match events of which 'NAME' matches, depending on the + argument of the option:--type option: + -- -With the option:--domain=++kernel++ or option:--domain=++user++ option, with the option:--type=++tracepoint++ option or without the option:--type option::: +`kernel:tracepoint`:: +`user:tracepoint`:: The full name of the LTTng tracepoint. -With the option:--domain=++jul++, option:--domain=++log4j++, or option:--domain=++python++ option::: +`jul:logging`:: +`log4j:logging`:: +`python:logging`:: The Java or Python logger name. -With the option:--domain=++kernel++ option and one of the option:--type=++syscall++, option:--type=++syscall:entry++, option:--type=++syscall:exit++, and option:--type=++syscall:entry+exit++ options::: +`kernel:syscall:entry`:: +`kernel:syscall:exit`:: +`kernel:syscall:entry+exit`:: The name of the system call, without any `sys_` prefix. -- + -This option is :not: available with the option:--type=++kprobe++ and -option:--type=++uprobe++ options. +This option is :not: available with other instrumentation point types. + As of LTTng{nbsp}{lttng_version}, not specifying this option is equivalent to specifying option:--name=++\'*\'++ (when it applies), but @@ -712,7 +734,7 @@ Only match events of which 'XNAME' does :not: match the full name of the LTTng user space tracepoint. + -Only available with the option:--domain=++user++ option. +Only available with the option:--type=++user:tracepoint++ option. 'NAME' and 'XNAME' are globbing patterns: the `*` character means ``match anything''. To match a literal `*` character, use :escwc:. @@ -720,8 +742,8 @@ Instrumentation point log level condition ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -See the <> section above. +See the ``<>'' section above. option:-l 'LOGLEVELSPEC', option:--log-level='LOGLEVELSPEC':: Only match events of which the log level of the LTTng tracepoint or @@ -738,8 +760,14 @@ Anything. -- + -This option is :not: available with the option:--domain=++kernel++ -option. +This option is :not: available with the following options: ++ +* option:--type=++kernel:tracepoint++ +* option:--type=++kernel:syscall:entry++ +* option:--type=++kernel:syscall:exit++ +* option:--type=++kernel:syscall:entry+exit++ +* option:--type=++kernel:kprobe++ +* option:--type=++kernel:uprobe++ + As of LTTng{nbsp}{lttng_version}, not specifying this option is equivalent to specifying option:--log-level=++..++ (when it applies), @@ -748,7 +776,7 @@ Event payload and context filter condition ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -See the <> +See the ``<>'' section above. option:-f 'EXPR', option:--filter='EXPR':: @@ -757,11 +785,10 @@ + This option is only available with the following options: + -* option:--type=++tracepoint++ -* option:--type=++syscall++ -* option:--type=++syscall:entry++ -* option:--type=++syscall:exit++ -* option:--type=++syscall:entry+exit++ +* option:--type=++kernel:tracepoint++ +* option:--type=++kernel:syscall:entry++ +* option:--type=++kernel:syscall:exit++ +* option:--type=++kernel:syscall:entry+exit++ include::common-footer.txt[] diff -Nru ltt-control-2.13~pre/doc/man/lttng-list.1.txt ltt-control-2.13~pre/doc/man/lttng-list.1.txt --- ltt-control-2.13~pre/doc/man/lttng-list.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-list.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,26 +1,27 @@ lttng-list(1) ============= -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME ---- -lttng-list - List LTTng tracing sessions and instrumentation points +lttng-list - List LTTng recording sessions and instrumentation points SYNOPSIS -------- -List the tracing sessions: +List the recording sessions: [verse] *lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *list* -List the tracing domains of a tracing session with at least one channel: +List the tracing domains of a recording session with at least one +channel: [verse] *lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *list* option:--domain 'SESSION' -List the channels and recording event rules of a tracing session: +List the channels and recording event rules of a recording session: [verse] *lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *list* [option:--channel='CHANNEL'] 'SESSION' @@ -39,27 +40,27 @@ The `lttng list` command lists: Without arguments:: - The tracing sessions of your Unix user, or of all users + The recording sessions of your Unix user, or of all users if your Unix user is `root`, within the connected session daemon. + See the ``Session daemon connection'' section of man:lttng(1) to learn how a user application connects to a session daemon. + -The command shows tracing session properties such as their output +The command shows recording session properties such as their output directories/URLs and whether or not they're active. With the 'SESSION' argument:: With the option:--domain option::: - The tracing domains (with at least one channel) of the tracing + The tracing domains (with at least one channel) of the recording session named 'SESSION'. Without the option:--domain option::: With the option:--channel='CHANNEL' option:::: The recording event rules of the channel 'CHANNEL' of the - tracing session named 'SESSION'. + recording session named 'SESSION'. Without the option:--channel option:::: - The channels of the tracing session named 'SESSION' and + The channels of the recording session named 'SESSION' and their recording event rules. + Use the dedicated tracing domain options (option:--kernel, @@ -84,12 +85,12 @@ Also list the available instrumentation point fields with the option:--fields option. -See man:lttng-concept(7) to learn more about tracing sessions, tracing +See man:lttng-concept(7) to learn more about recording sessions, tracing domains, channels, recording event rules, and instrumentation points. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. -List the channels and recording event rules of the current tracing +List the channels and recording event rules of the current recording session (see man:lttng-concept(7) to learn more) with the man:lttng-status(1) command. @@ -143,7 +144,7 @@ Only available with the 'SESSION' argument. option:-d, option:--domain:: - Show the tracing domains with at least one channel of the tracing + Show the tracing domains with at least one channel of the recording session named 'SESSION'. option:-f, option:--fields:: @@ -164,7 +165,7 @@ [[examples]] EXAMPLES -------- -.List the tracing sessions. +.List the recording sessions. ==== [role="term"] ---- @@ -172,7 +173,7 @@ ---- ==== -.Show the details of a specific tracing session. +.Show the details of a specific recording session. ==== [role="term"] ---- @@ -198,7 +199,7 @@ ---- ==== -.List the tracing domains of a specific tracing session having at least one channel. +.List the tracing domains of a specific recording session having at least one channel. ==== See the option:--domain option. @@ -208,7 +209,7 @@ ---- ==== -.Show the details of a specific channel in a specific tracing session. +.Show the details of a specific channel in a specific recording session. ==== See the option:--channel option. diff -Nru ltt-control-2.13~pre/doc/man/lttng-load.1.txt ltt-control-2.13~pre/doc/man/lttng-load.1.txt --- ltt-control-2.13~pre/doc/man/lttng-load.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-load.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,11 +1,11 @@ lttng-load(1) ============= -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME ---- -lttng-load - Load LTTng tracing session configurations +lttng-load - Load LTTng recording session configurations SYNOPSIS @@ -18,21 +18,21 @@ DESCRIPTION ----------- The `lttng load` command loads the configurations of one or more -tracing sessions from files. +recording sessions from files. -See man:lttng-concepts(7) to learn more about tracing sessions. +See man:lttng-concepts(7) to learn more about recording sessions. Use the `load` command in conjunction with the man:lttng-save(1) command -to save and restore the complete configurations of tracing sessions. A -tracing session configuration includes the enabled channels and -recording event rules, the context fields to be recorded, the tracing +to save and restore the complete configurations of recording sessions. A +recording session configuration includes the enabled channels and +recording event rules, the context fields to be recorded, the recording activity, and more. -Once LTTng loads one or more tracing session configurations, they appear -exactly as they were saved from the user's point of view. +Once LTTng loads one or more recording session configurations, they +appear exactly as they were saved from the user's point of view. LTTng searches the following directories, non-recursively, in this order -for tracing session configuration files: +for recording session configuration files: . `$LTTNG_HOME/.lttng/sessions` (`$LTTNG_HOME` defaults to `$HOME`) . +{system_sessions_dir}+ @@ -43,63 +43,63 @@ A directory:: With the 'SESSION' argument::: - LTTng searches for the tracing session configuration named + LTTng searches for the recording session configuration named 'SESSION' in all the files of the directory 'PATH' and loads it if found. Without the 'SESSION' argument::: - The option:--all option is implicit: LTTng loads all the tracing - session configurations found in all the files in the directory - 'PATH'. + The option:--all option is implicit: LTTng loads all the + recording session configurations found in all the files in the + directory 'PATH'. A file:: With the 'SESSION' argument::: - LTTng searches for the tracing session configuration named + LTTng searches for the recording session configuration named 'SESSION' in the file 'PATH' and loads it if found. Without the 'SESSION' argument::: - The option:--all option is implicit: LTTng loads all the tracing - session configurations found in the file 'PATH'. + The option:--all option is implicit: LTTng loads all the + recording session configurations found in the file 'PATH'. -Override the output URL of the loaded tracing session configurations +Override the output URL of the loaded recording session configurations with the option:--override-url option. -With the 'SESSION' argument, override the name of the loaded tracing +With the 'SESSION' argument, override the name of the loaded recording session configuration with the option:--override-name option. -By default, the `load` command does :not: overwrite existing tracing +By default, the `load` command does :not: overwrite existing recording sessions: the command fails. Allow the `load` command to overwrite -existing tracing sessions with the option:--force option. +existing recording sessions with the option:--force option. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. include::common-lttng-cmd-options-head.txt[] option:-a, option:--all:: - Load all the tracing session configurations (default). + Load all the recording session configurations (default). option:-f, option:--force:: - Overwrite existing tracing sessions when loading. + Overwrite existing recording sessions when loading. option:-i 'PATH', option:--input-path='PATH':: - Load tracing session configurations from 'PATH', either a directory - or a file, instead of loading them from the default search + Load recording session configurations from 'PATH', either a + directory or a file, instead of loading them from the default search directories. option:--override-name='NAME':: - Override the name of the loaded tracing session configuration, + Override the name of the loaded recording session configuration, 'SESSION', with 'NAME'. option:--override-url='URL':: - Override the output URL of the loaded tracing session configurations - with 'URL'. + Override the output URL of the loaded recording session + configurations with 'URL'. + This is the equivalent of the nloption:--set-url option of man:lttng-create(1). The validity of the URL override depends on the -type of tracing session configurations to load. This option applies to -_all_ the loaded tracing session configurations. +type of recording session configurations to load. This option applies to +_all_ the loaded recording session configurations. include::common-lttng-cmd-help-options.txt[] @@ -111,7 +111,7 @@ [[examples]] EXAMPLES -------- -.Load all the tracing session configurations from the default search directories. +.Load all the recording session configurations from the default search directories. ==== [role="term"] ---- @@ -119,7 +119,7 @@ ---- ==== -.Load all the tracing session configurations from a specific directory. +.Load all the recording session configurations from a specific directory. ==== See the option:--input-path option. @@ -129,7 +129,7 @@ ---- ==== -.Load a specific tracing session configuration from the default search directories. +.Load a specific recording session configuration from the default search directories. ==== [role="term"] ---- @@ -137,7 +137,7 @@ ---- ==== -.Allow LTTng to overwrite existing tracing sessions when loading. +.Allow LTTng to overwrite existing recording sessions when loading. ==== See the option:--force option. @@ -147,7 +147,7 @@ ---- ==== -.Load a specific tracing session configuration from a specific file, overriding its name. +.Load a specific recording session configuration from a specific file, overriding its name. ==== See the option:--input-path and option:--override-name options. diff -Nru ltt-control-2.13~pre/doc/man/lttng-metadata.1.txt ltt-control-2.13~pre/doc/man/lttng-metadata.1.txt --- ltt-control-2.13~pre/doc/man/lttng-metadata.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-metadata.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,11 +1,11 @@ lttng-metadata(1) ================= -:revdate: 30 April 2021 +:revdate: 14 June 2021 NAME ---- -lttng-metadata - Manage the metadata generation of an LTTng tracing session +lttng-metadata - Manage the metadata generation of an LTTng recording session SYNOPSIS @@ -24,9 +24,9 @@ option:-s 'SESSION', option:--session='SESSION':: - Manage the metadata generation of the tracing session named - 'SESSION' instead of the current tracing session (see - man:lttng-concepts(7) to learn more about the current tracing + Manage the metadata generation of the recording session named + 'SESSION' instead of the current recording session (see + man:lttng-concepts(7) to learn more about the current recording session). diff -Nru ltt-control-2.13~pre/doc/man/lttng-regenerate.1.txt ltt-control-2.13~pre/doc/man/lttng-regenerate.1.txt --- ltt-control-2.13~pre/doc/man/lttng-regenerate.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-regenerate.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,21 +1,21 @@ lttng-regenerate(1) =================== -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME ---- -lttng-regenerate - Regenerate specific data of an LTTng tracing session +lttng-regenerate - Regenerate specific data of an LTTng recording session SYNOPSIS -------- -Regenerate the metadata of a tracing session: +Regenerate the metadata of a recording session: [verse] *lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *regenerate metadata* [option:--session='SESSION'] -Regenerate the state dump event records of a tracing session: +Regenerate the state dump event records of a recording session: [verse] *lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *regenerate statedump* [option:--session='SESSION'] @@ -26,43 +26,42 @@ The `lttng regenerate` command regenerates specific data of: With the option:--session='SESSION' option:: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. Without the option:--session option:: - The current tracing session (see man:lttng-concepts(7) to learn more - about the current tracing session). + The current recording session (see man:lttng-concepts(7) to learn + more about the current recording session). -See man:lttng-concepts(7) to learn more about tracing sessions. +See man:lttng-concepts(7) to learn more about recording sessions. As of this version, the `metadata` and `statedump` targets are available. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. -Regenerate the metadata of a tracing session -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Regenerate the metadata of a recording session +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Use the `metadata` target to resample the offset between the monotonic clock and the wall time of the system, and then regenerate the metadata stream files. -More specifically, you may want to resample the wall time -following a major -link:https://en.wikipedia.org/wiki/Network_Time_Protocol[NTP] +More specifically, you may want to resample the wall time following a +major link:https://en.wikipedia.org/wiki/Network_Time_Protocol[NTP] correction. As such, LTTng can trace a system booting with an incorrect wall time before its wall time is NTP-corrected. Regenerating the -metadata of the selected tracing session ensures that trace readers can -accurately determine the event record timestamps relative to the +metadata of the selected recording session ensures that trace readers +can accurately determine the event record timestamps relative to the Unix epoch. Note that if you plan to rotate (see man:lttng-concepts(7) to learn -more) the selected tracing session, this target only regenerates the +more) the selected recording session, this target only regenerates the metadata stream files of the current and next trace chunks. [IMPORTANT] ==== You can only use the `metadata` target when the selected -tracing session: +recording session: * Is not in live mode (nloption:--live option of man:lttng-create(1)). @@ -75,12 +74,12 @@ ==== -Regenerate the state dump event records of a tracing session -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Regenerate the state dump event records of a recording session +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Use the `statedump` target to collect up-to-date state dump information and create corresponding event records. -This is particularly useful if the selected tracing session is in +This is particularly useful if the selected recording session is in snapshot mode (nloption:--snapshot option of the man:lttng-create(1) command) or if LTTng rotates trace files for one of its channels (see man:lttng-concepts(7)): in both cases, the state dump information may be @@ -91,8 +90,8 @@ option:-s 'SESSION', option:--session='SESSION':: - Regenerate specific data of the tracing session named 'SESSION' - instead of the current tracing session. + Regenerate specific data of the recording session named 'SESSION' + instead of the current recording session. include::common-lttng-cmd-help-options.txt[] @@ -104,7 +103,7 @@ [[examples]] EXAMPLES -------- -.Regenerate the metadata of the current tracing session. +.Regenerate the metadata of the current recording session. ==== [role="term"] ---- @@ -112,7 +111,7 @@ ---- ==== -.Regenerate the state dump event records of a specific tracing session. +.Regenerate the state dump event records of a specific recording session. ==== See the option:--session option. diff -Nru ltt-control-2.13~pre/doc/man/lttng-relayd.8.txt ltt-control-2.13~pre/doc/man/lttng-relayd.8.txt --- ltt-control-2.13~pre/doc/man/lttng-relayd.8.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-relayd.8.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,6 +1,6 @@ lttng-relayd(8) =============== -:revdate: 30 April 2021 +:revdate: 14 June 2021 :daemon-bin-name: lttng-relayd :daemon-ini-section: relayd @@ -29,12 +29,12 @@ writes it to the local file system. The relay daemon also accepts LTTng live connections from compatible readers (for example, man:babeltrace2(1)); this is the recommended approach to read trace data -while the remote tracing session is active. +while the remote recording session is active. By default, a relay daemon listens on all network interfaces to receive trace data, but only on `localhost` for LTTng live connections. Override the listening URLs with the option:--control-port, option:--data-port, -and option:--live-port options (see the <> +and option:--live-port options (see the ``<>'' section below). For example, use the option:--live-port=+tcp://0.0.0.0:{default_network_viewer_port}+ option to make a relay daemon listen to LTTng live connections on all network @@ -70,9 +70,9 @@ * Its configuration. + -See the <> section above. +See the ``<>'' section above. -* The tracing session configuration of the connected peer. +* The recording session configuration of the connected peer. * The LTTng session daemon (see man:lttng-sessiond(8)) version of the connected peer. @@ -86,10 +86,10 @@ Hostname of the connected peer. 'SESSION':: - Tracing session name. + Recording session name. 'DATETIME':: - Unique tracing session date/time. + Unique recording session date/time. 'TRACEDIR':: Custom trace directory path ('TRACEDIR' part of the argument of the @@ -112,7 +112,7 @@ [verse] 'BASE'/'HOSTNAME'/'TRACEDIR' -With the option:--group-output-by-session option (tracing session grouping):: +With the option:--group-output-by-session option (recording session grouping):: Without a custom trace directory::: 'SESSIONDV' is at least{nbsp}2.4:::: + @@ -180,7 +180,7 @@ addition to the default configuration files and the command-line options. + -See the <> section above. +See the ``<>'' section above. option:-d, option:--daemonize:: Start as a Unix daemon and close file descriptors (console). @@ -230,7 +230,7 @@ Output ~~~~~~ -See the <> section above to learn +See the ``<>'' section above to learn more. option:-p, option:--group-output-by-host:: @@ -240,8 +240,8 @@ strategy, but this may change in the future. option:-s, option:--group-output-by-session:: - Group the written trace directories by tracing session name instead - of by hostname. + Group the written trace directories by recording session name + instead of by hostname. option:-o 'DIR', option:--output='DIR':: Set the base output directory of the written trace directories to @@ -250,8 +250,8 @@ Ports ~~~~~ -See the <> section above to learn more about the -syntax of the 'URL' argument of the following options. +See the ``<>'' section above to learn more about +the syntax of the 'URL' argument of the following options. option:-C 'URL', option:--control-port='URL':: Listen to control data on URL 'URL'. diff -Nru ltt-control-2.13~pre/doc/man/lttng-remove-trigger.1.txt ltt-control-2.13~pre/doc/man/lttng-remove-trigger.1.txt --- ltt-control-2.13~pre/doc/man/lttng-remove-trigger.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-remove-trigger.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -27,7 +27,7 @@ user. If your Unix user is `root`, you can remove the trigger of another user with the option:--owner-uid option. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. OPTIONS diff -Nru ltt-control-2.13~pre/doc/man/lttng-rotate.1.txt ltt-control-2.13~pre/doc/man/lttng-rotate.1.txt --- ltt-control-2.13~pre/doc/man/lttng-rotate.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-rotate.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,11 +1,11 @@ lttng-rotate(1) =============== -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME ---- -lttng-rotate - Archive the current trace chunk of an LTTng tracing session +lttng-rotate - Archive the current trace chunk of an LTTng recording session SYNOPSIS @@ -20,29 +20,29 @@ the current trace chunk of: With the 'SESSION' argument:: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. Without the 'SESSION' argument:: - The current tracing session (see man:lttng-concepts(7) to learn more - about the current tracing session). + The current recording session (see man:lttng-concepts(7) to learn + more about the current recording session). -This action is called a _tracing session rotation_. +This action is called a _recording session rotation_. -See man:lttng-concepts(7) to learn more about the tracing session +See man:lttng-concepts(7) to learn more about the recording session rotation and trace chunk concepts. You can use the `rotate` command: -* Any time the tracing session is active. +* Any time the recording session is active. -* A single time once the tracing session becomes inactive. +* A single time once the recording session becomes inactive. See man:lttng-concepts(7) to learn more about the activity of a -tracing session. +recording session. By default, the `rotate` command ensures that LTTng finished performing -the tracing session rotation before it prints the path of the archived -trace chunk and exits. The printed path is absolute when the tracing +the recording session rotation before it prints the path of the archived +trace chunk and exits. The printed path is absolute when the recording session was created in normal mode and relative to the base output directory of the relay daemon (see the nloption:--output option of man:lttng-relayd(8)) when it was created in network streaming mode (see @@ -53,23 +53,23 @@ becomes archived, and the command does :not: print the path of the archived trace chunk. -Because LTTng flushes the current sub-buffers of the selected tracing -session when it performs a tracing session rotation, archived trace +Because LTTng flushes the current sub-buffers of the selected recording +session when it performs a recording session rotation, archived trace chunks are never redundant, that is, they do not overlap over time like snapshots can (see man:lttng-snapshot(1)). Also, a rotation does :not: directly cause discarded event records or packets. -A `rotate-session` trigger action can also rotate a tracing session (see -man:lttng-add-trigger(1)). +A `rotate-session` trigger action can also rotate a recording session +(see man:lttng-add-trigger(1)). -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. [IMPORTANT] ==== You may only use the `rotate` command when: -* The selected tracing session was created in normal mode or in network - streaming mode (see man:lttng-create(1)). +* The selected recording session was created in normal mode or in + network streaming mode (see man:lttng-create(1)). * No channel was created with a configured trace file count or size limit (see the nloption:--tracefile-size and @@ -85,7 +85,7 @@ option:-n, option:--no-wait:: - Do not ensure that the tracing session rotation operation is + Do not ensure that the recording session rotation operation is completed before exiting. @@ -98,7 +98,7 @@ [[examples]] EXAMPLES -------- -.Rotate the current tracing session. +.Rotate the current recording session. ==== [role="term"] ---- @@ -106,7 +106,7 @@ ---- ==== -.Rotate a specific tracing session. +.Rotate a specific recording session. ==== [role="term"] ---- @@ -114,7 +114,7 @@ ---- ==== -.Rotate the current tracing session without waiting for completion. +.Rotate the current recording session without waiting for completion. ==== See the option:--no-wait option. diff -Nru ltt-control-2.13~pre/doc/man/lttng-save.1.txt ltt-control-2.13~pre/doc/man/lttng-save.1.txt --- ltt-control-2.13~pre/doc/man/lttng-save.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-save.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,11 +1,11 @@ lttng-save(1) ============= -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME ---- -lttng-save - Save LTTng tracing session configurations +lttng-save - Save LTTng recording session configurations SYNOPSIS @@ -20,10 +20,10 @@ The `lttng save` command saves to files the configurations of: With the 'SESSION' argument:: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. Without the 'SESSION' argument:: - Implicit option:--all option: *all* the tracing sessions of the + Implicit option:--all option: *all* the recording sessions of the connected session daemon for your Unix user, or for all users if your Unix user is `root`, as listed in the output of `lttng list` (see man:lttng-list(1)). @@ -31,44 +31,44 @@ See the ``Session daemon connection'' section of man:lttng(1) to learn how a user application connects to a session daemon. -See man:lttng-concepts(7) to learn more about tracing sessions. +See man:lttng-concepts(7) to learn more about recording sessions. Use the `save` command in conjunction with the man:lttng-load(1) command -to save and restore the complete configurations of tracing sessions. +to save and restore the complete configurations of recording sessions. -The `save` command does :not: save tracing data, only the tracing +The `save` command does :not: save tracing data, only the recording session parameters, including the channel and recording event rule configurations. The default output directory path is `$LTTNG_HOME/.lttng/sessions` (`$LTTNG_HOME` defaults to `$HOME`). Override the default output -directory path with the option:--output-path option. Each tracing +directory path with the option:--output-path option. Each recording session configuration file is named __SNAME__++.lttng++, -where{nbsp}__SNAME__ is the original tracing session name. +where{nbsp}__SNAME__ is the original recording session name. -By default, the `save` command does :not: overwrite existing tracing +By default, the `save` command does :not: overwrite existing recording session configuration files: the command fails. Allow the `save` command -to overwrite existing tracing session configuration files with the +to overwrite existing recording session configuration files with the option:--force option. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. include::common-lttng-cmd-options-head.txt[] option:-a, option:--all:: - Save all the tracing session configurations of your Unix user, or of - all users if your Unix user is `root`, as listed in the output of - man:lttng-list(1), instead of the current tracing session or the - tracing session named 'SESSION'. + Save all the recording session configurations of your Unix user, or + of all users if your Unix user is `root`, as listed in the output of + man:lttng-list(1), instead of the current recording session or the + recording session named 'SESSION'. option:-f, option:--force:: - Overwrite existing tracing session configuration files when + Overwrite existing recording session configuration files when saving. option:-o 'DIR', option:--output-path='DIR':: - Save tracing session configuration files to the directory 'DIR' + Save recording session configuration files to the directory 'DIR' instead of `$LTTNG_HOME/.lttng/sessions` (`$LTTNG_HOME` defaults to `$HOME`). @@ -82,7 +82,7 @@ [[examples]] EXAMPLES -------- -.Save all the tracing session configurations to the default output directory. +.Save all the recording session configurations to the default output directory. ==== [role="term"] ---- @@ -90,7 +90,7 @@ ---- ==== -.Save a specific tracing session configuration to a specific output directory. +.Save a specific recording session configuration to a specific output directory. ==== See the option:--output-path option. @@ -100,7 +100,7 @@ ---- ==== -.Allow LTTng to overwrite existing tracing session configuration files when saving. +.Allow LTTng to overwrite existing recording session configuration files when saving. ==== See the option:--force option. diff -Nru ltt-control-2.13~pre/doc/man/lttng-sessiond.8.txt ltt-control-2.13~pre/doc/man/lttng-sessiond.8.txt --- ltt-control-2.13~pre/doc/man/lttng-sessiond.8.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-sessiond.8.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,6 +1,6 @@ lttng-sessiond(8) ================= -:revdate: 21 April 2021 +:revdate: 14 June 2021 :daemon-bin-name: lttng-sessiond :daemon-ini-section: sessiond @@ -38,8 +38,8 @@ An LTTng session daemon, `lttng-sessiond`, is a program which: -* Manages tracing sessions (see man:lttng-concepts(7) to learn more - about tracing sessions). +* Manages recording sessions (see man:lttng-concepts(7) to learn more + about recording sessions). * Controls the various components (like tracers and consumer daemons) of LTTng. @@ -98,10 +98,10 @@ [[load]] -Tracing session configuration loading -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -When the session daemon starts, it loads tracing session configurations -from: +Recording session configuration loading +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +When the session daemon starts, it loads recording session +configurations from: Without the option:--load option:: In this order: @@ -114,8 +114,8 @@ . All the files in +{system_sessions_auto_dir}+. -- + -`lttng-sessiond` only loads tracing configuration files from the -directories above if its UID and their UID are the same. +`lttng-sessiond` only loads recording session configuration files from +the directories above if its UID and their UID are the same. With the option:--load='PATH' option:: 'PATH' is a directory::: @@ -143,7 +143,7 @@ addition to the default configuration files and the command-line options. + -See the <> section above. +See the ``<>'' section above. option:-d, option:--daemonize:: Start as a Unix daemon and close file descriptors (console). @@ -164,11 +164,12 @@ and, therefore, control LTTng kernel tracing. option:-l 'PATH', option:--load='PATH':: - Load tracing session configurations from 'PATH', either a directory - or a file, instead of loading them from the default search + Load recording session configurations from 'PATH', either a + directory or a file, instead of loading them from the default search directories. + -See the <> section above. +See the ``<>'' section +above. option:-S, option:--sig-parent:: Send the `USR1` signal to the parent process to notify readiness. @@ -379,7 +380,7 @@ Set to `0` or `-1` to use the timeout of the operating system (default). `LTTNG_SESSION_CONFIG_XSD_PATH`:: - Tracing session configuration XML schema definition (XSD) path. + Recording session configuration XML schema definition (XSD) path. FILES @@ -395,28 +396,28 @@ man:lttng-create(1) command. `$LTTNG_HOME/.lttng/sessions/auto`:: - Directory from which `lttng-sessiond` loads Unix user tracing + Directory from which `lttng-sessiond` loads Unix user recording session configurations when starting. + -See the <> section above to -learn more. +See the ``<>'' section +above to learn more. +{system_sessions_auto_dir}+:: - Directory from which `lttng-sessiond` loads system-wide tracing + Directory from which `lttng-sessiond` loads system-wide recording session configurations when starting. + -See the <> section above to -learn more. +See the ``<>'' section +above to learn more. `$LTTNG_HOME/.lttng/lttng.conf`:: Unix user's LTTng daemon INI configuration file. + -See the <> section above to learn more. +See the ``<>'' section above to learn more. +{system_lttng_conf}+:: System-wide LTTng daemon INI configuration file. + -See the <> section above to learn more. +See the ``<>'' section above to learn more. NOTE: `$LTTNG_HOME` defaults to `$HOME`. diff -Nru ltt-control-2.13~pre/doc/man/lttng-set-session.1.txt ltt-control-2.13~pre/doc/man/lttng-set-session.1.txt --- ltt-control-2.13~pre/doc/man/lttng-set-session.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-set-session.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,11 +1,11 @@ lttng-set-session(1) ==================== -:revdate: 29 April 2021 +:revdate: 14 June 2021 NAME ---- -lttng-set-session - Set the current LTTng tracing session +lttng-set-session - Set the current LTTng recording session SYNOPSIS @@ -16,15 +16,16 @@ DESCRIPTION ----------- -The `lttng set-session` command sets the current tracing session of your -Unix user to the tracing session named 'SESSION'. +The `lttng set-session` command sets the current recording session of your +Unix user to the recording session named 'SESSION'. -See man:lttng-concepts(7) to learn more about the current tracing session. +See man:lttng-concepts(7) to learn more about the current recording +session. The `set-session` command effectively updates the `$LTTNG_HOME/.lttngrc` file. -List the tracing sessions of your Unix user, or of all users if +List the recording sessions of your Unix user, or of all users if your Unix user is `root`, within the connected session daemon with the man:lttng-list(1) command. diff -Nru ltt-control-2.13~pre/doc/man/lttng-snapshot.1.txt ltt-control-2.13~pre/doc/man/lttng-snapshot.1.txt --- ltt-control-2.13~pre/doc/man/lttng-snapshot.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-snapshot.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,35 +1,35 @@ lttng-snapshot(1) ================= -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME ---- -lttng-snapshot - Take a snapshot of an LTTng tracing session +lttng-snapshot - Take a snapshot of an LTTng recording session SYNOPSIS -------- -Take a tracing session snapshot: +Take a recording session snapshot: [verse] *lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *snapshot* *record* [option:--max-size='SIZE'] [option:--name='NAME'] [option:--session='SESSION'] [option:--ctrl-url='URL' option:--data-url='URL' | 'URL'] -Add a snapshot output to a tracing session: +Add a snapshot output to a recording session: [verse] *lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *snapshot* *add-output* [option:--max-size='SIZE'] [option:--name='NAME'] [option:--session='SESSION'] (option:--ctrl-url='URL' option:--data-url='URL' | 'URL') -Show the snapshot output of a tracing session: +Show the snapshot output of a recording session: [verse] *lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *snapshot* *list-output* [option:--session='SESSION'] -Remove the snapshot output from a tracing session: +Remove the snapshot output from a recording session: [verse] *lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *snapshot* *del-output* [option:--session='SESSION'] *1* @@ -41,40 +41,40 @@ snapshot output, and show the snapshot output of: With the option:--session='SESSION' option:: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. Without the option:--session option:: - The current tracing session (see man:lttng-concepts(7) to learn more - about the current tracing session). + The current recording session (see man:lttng-concepts(7) to learn more + about the current recording session). -See man:lttng-concepts(7) to learn more about tracing sessions. +See man:lttng-concepts(7) to learn more about recording sessions. A _snapshot_ is a dump of the current sub-buffers of all the channels of -the selected tracing session. +the selected recording session. When LTTng takes a snapshot, it sends the sub-buffer dump of the -selected tracing session to the local file system or over the network to -a listening relay daemon (man:lttng-relayd(8)). See the -<> section below to learn more. +selected recording session to the local file system or over the network +to a listening relay daemon (man:lttng-relayd(8)). See the +``<>'' section below to learn more. When LTTng takes a snapshot, it does :not: clear the sub-buffers of the -selected tracing session. In other words, different snapshots of the -selected tracing session can contain the same event records. +selected recording session. In other words, different snapshots of the +selected recording session can contain the same event records. -You must have created the selected tracing session in snapshot mode (see -the nloption:--snapshot option of the man:lttng-create(1) command as -well as man:lttng-concepts(7) to learn more about tracing session modes) -to use the `snapshot` command. +You must have created the selected recording session in snapshot mode +(see the nloption:--snapshot option of the man:lttng-create(1) command +as well as man:lttng-concepts(7) to learn more about recording session +modes) to use the `snapshot` command. -A `snapshot-session` trigger action can also take a tracing session +A `snapshot-session` trigger action can also take a recording session snapshot (see man:lttng-add-trigger(1)). -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. If you want, instead, to keep all the trace data, but divide it into archived chunks which are then, like snapshots, ready to be processed, -see the tracing session rotation feature in man:lttng-concepts(7). Trace -chunk archives do :not: overlap like snapshots can. +see the recording session rotation feature in man:lttng-concepts(7). +Trace chunk archives do :not: overlap like snapshots can. [NOTE] ==== @@ -84,15 +84,15 @@ the tracers overwriting unconsumed trace packets during the snapshot operation. -After LTTng writes the snapshot trace data, you can restart the tracing -session with the man:lttng-start(1) command. +After LTTng writes the snapshot trace data, you can restart the +recording session with the man:lttng-start(1) command. ==== [[output]] Snapshot output ~~~~~~~~~~~~~~~ -When you take a tracing session snapshot with the `record` action, LTTng +When you take a recording session snapshot with the `record` action, LTTng writes the snapshot trace files to: If you specify the 'URL' non-option argument or the option:--ctrl-url and option:--data-url options:: @@ -102,33 +102,33 @@ See man:lttng-create(1) for the format of 'URL'. Otherwise:: - The snapshot output of the selected tracing session. + The snapshot output of the selected recording session. + -Add a snapshot output to a tracing session with the `add-output` action. -As of LTTng{nbsp}{lttng_version}, you may only add one snapshot output -to a given tracing session. +Add a snapshot output to a recording session with the `add-output` +action. As of LTTng{nbsp}{lttng_version}, you may only add one snapshot +output to a given recording session. + -When you create a snapshot mode tracing session with the +When you create a snapshot mode recording session with the nloption:--snapshot option of the man:lttng-create(1) command, and without its nloption:--no-output option, the `create` command automatically adds a snapshot output named `snapshot-1` to the created -tracing session: +recording session: + -- With its nloption:--output, nloption:--set-url, nloption:--ctrl-url, or nloption:--data-url options:: Equivalent to using the `add-output` action with the provided or - equivalent URL(s) immediately after creating the tracing session. + equivalent URL(s) immediately after creating the recording session. Otherwise:: A subdirectory, under the `$LTTNG_HOME/lttng-traces` (`$LTTNG_HOME` defaults to `$HOME`) directory, of which the name contains the - tracing session name and the date/time. + recording session name and the date/time. -- + -Show the current snapshot output of a tracing session with the +Show the current snapshot output of a recording session with the `list-output` action. + -Remove the snapshot output of a tracing session with the +Remove the snapshot output of a recording session with the `del-output` action. For both the `record` and `add-output` actions: @@ -140,7 +140,7 @@ to this output. * By default, the snapshot files can be as big as the sum of the sizes - of all the sub-buffers of all the channels of the selected tracing + of all the sub-buffers of all the channels of the selected recording session. + Set the maximum total size of all the snapshot trace files LTTng writes @@ -153,13 +153,13 @@ Recording target ~~~~~~~~~~~~~~~~ option:-s 'SESSION', option:--session='SESSION':: - Take a snapshot of the sub-buffers of the tracing session named - 'SESSION' instead of the current tracing session. + Take a snapshot of the sub-buffers of the recording session named + 'SESSION' instead of the current recording session. Output ~~~~~~ -See the <> section above. +See the ``<>'' section above. option:-C 'URL', option:--ctrl-url='URL':: Set the control path URL to 'URL'. @@ -195,7 +195,7 @@ [[examples]] EXAMPLES -------- -.Take a snapshot of the current tracing session, sending the trace files to its snapshot output. +.Take a snapshot of the current recording session, sending the trace files to its snapshot output. ==== [role="term"] ---- @@ -203,7 +203,7 @@ ---- ==== -.Take a snapshot of a specific tracing session, giving it a custom name. +.Take a snapshot of a specific recording session, giving it a custom name. ==== See the option:--session and option:--name options. @@ -213,7 +213,7 @@ ---- ==== -.Take a snapshot of the current tracing session, sending the trace files to a custom location. +.Take a snapshot of the current recording session, sending the trace files to a custom location. ==== See the ``Output directory'' section of man:lttng-relayd(8) to understand where the relay daemon to connect to (`3.96.87.215`) writes @@ -225,7 +225,7 @@ ---- ==== -.Replace the snapshot output of a specific tracing session with a local file system path. +.Replace the snapshot output of a specific recording session with a local file system path. ==== See the option:--session option. @@ -237,7 +237,7 @@ ---- ==== -.Take a snapshot of the current tracing session, making sure its size is not over 4{nbsp}MiB. +.Take a snapshot of the current recording session, making sure its size is not over 4{nbsp}MiB. ==== See the option:--max-size option. diff -Nru ltt-control-2.13~pre/doc/man/lttng-start.1.txt ltt-control-2.13~pre/doc/man/lttng-start.1.txt --- ltt-control-2.13~pre/doc/man/lttng-start.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-start.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,11 +1,11 @@ lttng-start(1) ============== -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME ---- -lttng-start - Start an LTTng tracing session +lttng-start - Start an LTTng recording session SYNOPSIS @@ -16,27 +16,27 @@ DESCRIPTION ----------- -The `lttng start` command starts a tracing session, that is, it +The `lttng start` command starts a recording session, that is, it activates the LTTng tracers for: With the 'SESSION' argument:: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. Without the 'SESSION' argument:: - The current tracing session (see man:lttng-concepts(7) to learn more - about the current tracing session). + The current recording session (see man:lttng-concepts(7) to learn + more about the current recording session). -See man:lttng-concepts(7) to learn more about tracing sessions. +See man:lttng-concepts(7) to learn more about recording sessions. -The selected tracing session must be inactive (stopped). A tracing +The selected recording session must be inactive (stopped). A recording session is inactive on creation (see man:lttng-create(1)). -A `start-session` trigger action can also start a tracing session +A `start-session` trigger action can also start a recording session (see man:lttng-add-trigger(1)). -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. -Stop an active tracing session with the man:lttng-stop(1) command. +Stop an active recording session with the man:lttng-stop(1) command. include::common-lttng-cmd-options-head.txt[] @@ -51,7 +51,7 @@ [[examples]] EXAMPLES -------- -.Start the current tracing session. +.Start the current recording session. ==== [role="term"] ---- @@ -59,7 +59,7 @@ ---- ==== -.Start a specific tracing session. +.Start a specific recording session. ==== [role="term"] ---- diff -Nru ltt-control-2.13~pre/doc/man/lttng-status.1.txt ltt-control-2.13~pre/doc/man/lttng-status.1.txt --- ltt-control-2.13~pre/doc/man/lttng-status.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-status.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,11 +1,11 @@ lttng-status(1) =============== -:revdate: 29 April 2021 +:revdate: 14 June 2021 NAME ---- -lttng-status - Show the status of the current LTTng tracing session +lttng-status - Show the status of the current LTTng recording session SYNOPSIS @@ -16,16 +16,16 @@ DESCRIPTION ----------- -The `lttng status` command shows the status of the current tracing +The `lttng status` command shows the status of the current recording session (see man:lttng-concepts(7) to learn more about the current -tracing session). +recording session). This command is equivalent to: [verse] *lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *list* 'CURSESSION' -where `CURSESSION` is the name of the current tracing session. +where `CURSESSION` is the name of the current recording session. include::common-lttng-cmd-options-head.txt[] diff -Nru ltt-control-2.13~pre/doc/man/lttng-stop.1.txt ltt-control-2.13~pre/doc/man/lttng-stop.1.txt --- ltt-control-2.13~pre/doc/man/lttng-stop.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-stop.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,11 +1,11 @@ lttng-stop(1) ============= -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME ---- -lttng-stop - Stop an LTTng tracing session +lttng-stop - Stop an LTTng recording session SYNOPSIS @@ -16,51 +16,51 @@ DESCRIPTION ----------- -The `lttng stop` command stops a tracing session, that is, it +The `lttng stop` command stops a recording session, that is, it deactivates the LTTng tracers for: With the 'SESSION' argument:: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. Without the 'SESSION' argument:: - The current tracing session (see man:lttng-concepts(7) to learn more - about the current tracing session). + The current recording session (see man:lttng-concepts(7) to learn more + about the current recording session). -See man:lttng-concepts(7) to learn more about tracing sessions. +See man:lttng-concepts(7) to learn more about recording sessions. -The selected tracing session must be active (started; see -man:lttng-start(1)). A tracing session is inactive on creation (see +The selected recording session must be active (started; see +man:lttng-start(1)). A recording session is inactive on creation (see man:lttng-create(1)). -A `stop-session` trigger action can also stop a tracing session (see +A `stop-session` trigger action can also stop a recording session (see man:lttng-add-trigger(1)). -Start an inactive tracing session with the man:lttng-start(1) command. +Start an inactive recording session with the man:lttng-start(1) command. By default, the `stop` command ensures that the trace data of the -selected tracing session is valid before it exits. Make the command exit -immediately with the option:--no-wait option. In this case, however, the -traces(s) might not be valid when the command exits, and there's no way -to know when it/they becomes valid. +selected recording session is valid before it exits. Make the command +exit immediately with the option:--no-wait option. In this case, +however, the traces(s) might not be valid when the command exits, and +there's no way to know when it/they becomes valid. If LTTng archived the current trace chunk (see man:lttng-rotate(1) and -man:lttng-enable-rotation(1)) of the selected tracing session at least +man:lttng-enable-rotation(1)) of the selected recording session at least once during its lifetime, the `stop` command renames the current trace chunk subdirectory and prints the renamed path. Although it's safe to -read the content of this renamed subdirectory while the tracing session -remains inactive, it's :not: a trace chunk archive: you need to destroy -the tracing session with man:lttng-destroy(1) or perform a rotation with -man:lttng-rotate(1) to archive it. +read the content of this renamed subdirectory while the recording +session remains inactive, it's :not: a trace chunk archive: you need to +destroy the recording session with man:lttng-destroy(1) or perform a +rotation with man:lttng-rotate(1) to archive it. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. include::common-lttng-cmd-options-head.txt[] option:-n, option:--no-wait:: - Do :not: ensure that the trace data of the selected tracing session - is valid before exiting. + Do :not: ensure that the trace data of the selected recording + session is valid before exiting. include::common-lttng-cmd-help-options.txt[] @@ -72,7 +72,7 @@ [[examples]] EXAMPLES -------- -.Stop the current tracing session. +.Stop the current recording session. ==== [role="term"] ---- @@ -80,7 +80,7 @@ ---- ==== -.Stop a specific tracing session. +.Stop a specific recording session. ==== [role="term"] ---- @@ -88,7 +88,7 @@ ---- ==== -.Stop the current tracing session without waiting for completion. +.Stop the current recording session without waiting for completion. ==== See the option:--no-wait option. diff -Nru ltt-control-2.13~pre/doc/man/lttng-track.1.txt ltt-control-2.13~pre/doc/man/lttng-track.1.txt --- ltt-control-2.13~pre/doc/man/lttng-track.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-track.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,6 +1,6 @@ lttng-track(1) ============== -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME @@ -41,17 +41,17 @@ events based on their attributes within: With the option:--session='SESSION' option:: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. Without the option:--session option:: - The current tracing session (see man:lttng-concepts(7) to learn more - about the current tracing session). + The current recording session (see man:lttng-concepts(7) to learn + more about the current recording session). -See man:lttng-concepts(7) to learn more about tracing sessions and +See man:lttng-concepts(7) to learn more about recording sessions and recording event rules. The `track` command adds values to _inclusion sets_ of process -attributes. The available inclusion sets are, for a given tracing +attributes. The available inclusion sets are, for a given recording session: With the option:--kernel option:: @@ -83,12 +83,12 @@ When an event{nbsp}__E__ satisfies all the other explicit and implicit conditions of an event rule{nbsp}__ER__, __ER__ matches{nbsp}__E__ if the attributes of the process for which LTTng creates{nbsp}__E__ are -*all* part of the inclusion sets of the tracing session and domain +*all* part of the inclusion sets of the recording session and domain of{nbsp}__ER__. -By default, on tracing session creation (see man:lttng-create(1)), +By default, on recording session creation (see man:lttng-create(1)), all processes are allowed to record events. In other words, all the -inclusion sets of the tracing session contain all the possible +inclusion sets of the recording session contain all the possible process attribute values. If a given inclusion set{nbsp}__IS__ contains all the possible values @@ -111,7 +111,7 @@ $ lttng start ---- -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. Remove values from an inclusion set with the man:lttng-untrack(1) command. @@ -120,7 +120,7 @@ Inclusion set example ~~~~~~~~~~~~~~~~~~~~~ This example operates on the Linux kernel process ID (PID) inclusion set -of the current tracing session to show how an inclusion set works. +of the current recording session to show how an inclusion set works. Assume the maximum system PID is 7 for this example. @@ -189,15 +189,15 @@ Recording target ~~~~~~~~~~~~~~~~ option:-s 'SESSION', option:--session='SESSION':: - Add values to one or more inclusion sets of the tracing session - named 'SESSION' instead of the current tracing session. + Add values to one or more inclusion sets of the recording session + named 'SESSION' instead of the current recording session. Inclusion set selection ~~~~~~~~~~~~~~~~~~~~~~~ option:-p ['PID'[,'PID']...], option:--pid[='PID'[,'PID']...]:: For each 'PID' argument, add 'PID' to the process ID inclusion set - of the selected tracing session and domain. + of the selected recording session and domain. + 'PID' is the process ID attribute of a process as seen from the root PID namespace (see man:pid_namespaces(7)). @@ -206,14 +206,14 @@ option:--vpid[='VPID'[,'VPID']...]:: For each 'VPID' argument, add 'VPID' to the virtual process ID - inclusion set of the selected tracing session and domain. + inclusion set of the selected recording session and domain. + 'VPID' is the virtual process ID attribute of a process as seen from the PID namespace of the process (see man:pid_namespaces(7)). option:--uid[='USER'[,'USER']...]:: For each 'USER' argument, add 'USER' to the user ID inclusion set of - the selected tracing session and domain. + the selected recording session and domain. + 'USER' is either: + @@ -231,7 +231,7 @@ option:--vuid[='VUSER'[,'VUSER']...]:: For each 'VUSER' argument, add 'VUSER' to the virtual user ID - inclusion set of the selected tracing session and domain. + inclusion set of the selected recording session and domain. + 'VUSER' is either: + @@ -248,7 +248,7 @@ option:--gid[='GROUP'[,'GROUP']...]:: For each 'GROUP' argument, add 'GROUP' to the group ID - inclusion set of the selected tracing session and domain. + inclusion set of the selected recording session and domain. + 'GROUP' is either: + @@ -266,7 +266,7 @@ option:--vgid[='VGROUP'[,'VGROUP']...]:: For each 'VGROUP' argument, add 'VGROUP' to the virtual group ID - inclusion set of the selected tracing session and domain. + inclusion set of the selected recording session and domain. + 'VGROUP' is either: + @@ -299,7 +299,7 @@ [[examples]] EXAMPLES -------- -.Add the PIDs 1728 and 3775 to the Linux kernel process ID inclusion set of the current tracing session. +.Add the PIDs 1728 and 3775 to the Linux kernel process ID inclusion set of the current recording session. ==== See the option:--pid option. @@ -309,7 +309,7 @@ ---- ==== -.Add the ID of a specific user to the user space virtual user ID inclusion set of a specific tracing session. +.Add the ID of a specific user to the user space virtual user ID inclusion set of a specific recording session. ==== See the option:--vuid and option:--session options. @@ -319,7 +319,7 @@ ---- ==== -.Add all the possible group IDs to the Linux kernel group ID inclusion set of the current tracing session. +.Add all the possible group IDs to the Linux kernel group ID inclusion set of the current recording session. ==== See the option:--all and option:--gid options. diff -Nru ltt-control-2.13~pre/doc/man/lttng-untrack.1.txt ltt-control-2.13~pre/doc/man/lttng-untrack.1.txt --- ltt-control-2.13~pre/doc/man/lttng-untrack.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-untrack.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,6 +1,6 @@ lttng-untrack(1) ================ -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME @@ -40,27 +40,27 @@ LTTng events based on their attributes within: With the option:--session='SESSION' option:: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. Without the option:--session option:: - The current tracing session (see man:lttng-concepts(7) to learn more - about the current tracing session). + The current recording session (see man:lttng-concepts(7) to learn + more about the current recording session). -See man:lttng-concepts(7) to learn more about tracing sessions and +See man:lttng-concepts(7) to learn more about recording sessions and recording event rules. The `untrack` command removes values from _inclusion sets_ of process attributes. See man:lttng-track(1) to learn more about inclusion sets. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. Inclusion set example ~~~~~~~~~~~~~~~~~~~~~ -A common operation is to create a tracing session (see +A common operation is to create a recording session (see man:lttng-create(1)), remove all the entries from the Linux kernel -process ID inclusion set, start tracing, and then manually add PIDs -while the tracing session is active. +process ID inclusion set, start recording, and then manually add PIDs +while the recording session is active. Assume the maximum system PID is 7 for this example. @@ -137,15 +137,15 @@ Recording target ~~~~~~~~~~~~~~~~ option:-s 'SESSION', option:--session='SESSION':: - Remove values from one or more inclusion sets of the tracing session - named 'SESSION' instead of the current tracing session. + Remove values from one or more inclusion sets of the recording + session named 'SESSION' instead of the current recording session. Inclusion set selection ~~~~~~~~~~~~~~~~~~~~~~~ option:-p ['PID'[,'PID']...], option:--pid[='PID'[,'PID']...]:: For each 'PID' argument, remove 'PID' from the process ID inclusion - set of the selected tracing session and domain. + set of the selected recording session and domain. + 'PID' is the process ID attribute of a process as seen from the root PID namespace (see man:pid_namespaces(7)). @@ -154,14 +154,14 @@ option:--vpid[='VPID'[,'VPID']...]:: For each 'VPID' argument, remove 'VPID' from the virtual process ID - inclusion set of the selected tracing session and domain. + inclusion set of the selected recording session and domain. + 'VPID' is the virtual process ID attribute of a process as seen from the PID namespace of the process (see man:pid_namespaces(7)). option:--uid[='USER'[,'USER']...]:: For each 'USER' argument, remove 'USER' from the user ID inclusion - set of the selected tracing session and domain. + set of the selected recording session and domain. + 'USER' is either: + @@ -179,7 +179,7 @@ option:--vuid[='VUSER'[,'VUSER']...]:: For each 'VUSER' argument, remove 'VUSER' from the virtual user ID - inclusion set of the selected tracing session and domain. + inclusion set of the selected recording session and domain. + 'VUSER' is either: + @@ -196,7 +196,7 @@ option:--gid[='GROUP'[,'GROUP']...]:: For each 'GROUP' argument, remove 'GROUP' from the group ID - inclusion set of the selected tracing session and domain. + inclusion set of the selected recording session and domain. + 'GROUP' is either: + @@ -214,7 +214,7 @@ option:--vgid[='VGROUP'[,'VGROUP']...]:: For each 'VGROUP' argument, remove 'VGROUP' from the virtual group - ID inclusion set of the selected tracing session and domain. + ID inclusion set of the selected recording session and domain. + 'VGROUP' is either: + @@ -247,7 +247,7 @@ [[examples]] EXAMPLES -------- -.Remove the PIDs 1728 and 3775 from the Linux kernel process ID inclusion set of the current tracing session. +.Remove the PIDs 1728 and 3775 from the Linux kernel process ID inclusion set of the current recording session. ==== See the option:--pid option. @@ -257,7 +257,7 @@ ---- ==== -.Remove the IDs of a specific groups from the user space virtual group ID inclusion set of a specific tracing session. +.Remove the IDs of a specific groups from the user space virtual group ID inclusion set of a specific recording session. ==== See the option:--vgid and option:--session options. @@ -268,7 +268,7 @@ ---- ==== -.Remove all the user IDs from the Linux kernel user ID inclusion set of the current tracing session. +.Remove all the user IDs from the Linux kernel user ID inclusion set of the current recording session. ==== See the option:--all and option:--uid options. diff -Nru ltt-control-2.13~pre/doc/man/lttng-view.1.txt ltt-control-2.13~pre/doc/man/lttng-view.1.txt --- ltt-control-2.13~pre/doc/man/lttng-view.1.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/lttng-view.1.txt 2021-06-17 15:47:40.000000000 +0000 @@ -1,6 +1,6 @@ lttng-view(1) ============= -:revdate: 17 May 2021 +:revdate: 14 June 2021 NAME @@ -21,24 +21,24 @@ current traces of: With the option:--session='SESSION' option:: - The tracing session named 'SESSION'. + The recording session named 'SESSION'. With the option:--trace-path='DIR' option:: The local file system directory 'DIR'. Otherwise:: - The current tracing session (see man:concepts(1) to learn more about - the current tracing session). + The current recording session (see man:concepts(1) to learn more + about the current recording session). With the option:--session option or without the option:--trace-path -option, the mode of the selected tracing session may :not: be network +option, the mode of the selected recording session may :not: be network streaming or live. By default, the `view` command attempts to launch man:babeltrace2(1) or, if it's not available, man:babeltrace(1). Override which trace reader to launch with the option:--viewer option. -See the <> section below for usage examples. +See the ``<>'' section below for usage examples. include::common-lttng-cmd-options-head.txt[] @@ -46,7 +46,7 @@ option:-t 'DIR', option:--trace-path='DIR':: Pass 'DIR' as the last argument of the trace reader command instead - of the output directory of the selected tracing session. + of the output directory of the selected recording session. option:-e 'READER', option:--viewer='READER':: Use the trace reader 'READER' to read the traces. @@ -68,7 +68,7 @@ [[examples]] EXAMPLES -------- -.Read the traces of the current tracing session with Babeltrace. +.Read the traces of the current recording session with Babeltrace. ==== [role="term"] ---- @@ -76,7 +76,7 @@ ---- ==== -.Read the traces of a specific tracing session with a custom trace reader. +.Read the traces of a specific recording session with a custom trace reader. ==== See the option:--viewer option. diff -Nru ltt-control-2.13~pre/doc/man/manpage.xsl ltt-control-2.13~pre/doc/man/manpage.xsl --- ltt-control-2.13~pre/doc/man/manpage.xsl 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/man/manpage.xsl 2021-06-17 15:47:40.000000000 +0000 @@ -22,9 +22,6 @@ <> - - \fI\fR - diff -Nru ltt-control-2.13~pre/doc/python-howto.txt ltt-control-2.13~pre/doc/python-howto.txt --- ltt-control-2.13~pre/doc/python-howto.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/python-howto.txt 2021-06-17 15:47:40.000000000 +0000 @@ -34,7 +34,7 @@ >>> lttng.create("session-name", "path/to/trace") -4) Create a handle for the tracing session and domain +4) Create a handle for the recording session and domain >>> domain = lttng.Domain() >>> domain.type = lttng.DOMAIN_KERNEL * @@ -63,7 +63,7 @@ >>> lttng.stop("session-name") -7) Destroy the tracing session +7) Destroy the recording session >>> lttng.destroy("session-name") diff -Nru ltt-control-2.13~pre/doc/quickstart.txt ltt-control-2.13~pre/doc/quickstart.txt --- ltt-control-2.13~pre/doc/quickstart.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/quickstart.txt 2021-06-17 15:47:40.000000000 +0000 @@ -3,7 +3,7 @@ 2011-12-12: For user-space tracing, only the global UST domain ("-u" alone) is supported meaning that if you enable a tracepoint for user-space it will be -enabled for all applications for the current tracing session you are working +enabled for all applications for the current recording session you are working on. QUICKSTART @@ -23,8 +23,8 @@ lttng-tools provide a session daemon (lttng-sessiond) that acts as a tracing registry. To trace any instrumented applications or the kernel, a registered -tracing session is needed beforehand. To interact with the session daemon and a -tracing session, you should use the lttng command line UI (lttng). It is also +recording session is needed beforehand. To interact with the session daemon and a +recording session, you should use the lttng command line UI (lttng). It is also possible to use the liblttngctl library for tracing control (lttng.h). Here is a list of some powerful features the LTTng 2.0 kernel tracer offers: @@ -57,7 +57,7 @@ # lttng list -k -1) Create a tracing session. The .lttng directory will be created with .lttngrc +1) Create a recording session. The .lttng directory will be created with .lttngrc file in $HOME containing the session name (here 'mysession') you are working on. @@ -172,7 +172,7 @@ $ lttng list -u -1) Create a tracing session. The .lttng directory will be created with a +1) Create a recording session. The .lttng directory will be created with a .lttngrc file in $HOME containing the session name (here 'mysession') you are working on. diff -Nru ltt-control-2.13~pre/doc/streaming-howto.txt ltt-control-2.13~pre/doc/streaming-howto.txt --- ltt-control-2.13~pre/doc/streaming-howto.txt 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/doc/streaming-howto.txt 2021-06-17 15:47:40.000000000 +0000 @@ -48,7 +48,7 @@ Simple and quick network streaming. -1) Create a tracing session that will be streamed over the network for the +1) Create a recording session that will be streamed over the network for the specified domain. This session will contain, in our example, syscall events. # lttng create syscall-session @@ -83,12 +83,12 @@ This example uses all possible options to fine grained control the streaming. -1) Again, create a tracing session that will be streamed over the network for +1) Again, create a recording session that will be streamed over the network for the specified domain. # lttng create syscall-session -2) Set relayd URIs for the tracing session and kernel domain. +2) Set relayd URIs for the recording session and kernel domain. ONLY set the remote relayd URIs (both control and data at the same destination and using default ports) on the consumer but does not enable the consumer to use diff -Nru ltt-control-2.13~pre/extras/bindings/swig/python/lttng.i.in ltt-control-2.13~pre/extras/bindings/swig/python/lttng.i.in --- ltt-control-2.13~pre/extras/bindings/swig/python/lttng.i.in 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/extras/bindings/swig/python/lttng.i.in 2021-06-17 15:47:40.000000000 +0000 @@ -398,20 +398,20 @@ //Functions not needing redefinition %feature("docstring")"create(str name, str path) -> int -Create a new tracing session using name and path. +Create a new recording session using name and path. Returns 0 on success or a negative error code." int lttng_create_session(const char *name, const char *path); %feature("docstring")"create_snapshot(str name, str snapshot_url) -> int -Create a new tracing session using name and snapshot_url in snapshot +Create a new recording session using name and snapshot_url in snapshot mode (flight recorder). Returns 0 on success or a negative error code." int lttng_create_session_snapshot(const char *name, const char *path); %feature("docstring")"destroy(str name) -> int -Tear down tracing session using name. +Tear down recording session using name. Returns 0 on success or a negative error code." int lttng_destroy_session(const char *name); diff -Nru ltt-control-2.13~pre/include/lttng/error-query.h ltt-control-2.13~pre/include/lttng/error-query.h --- ltt-control-2.13~pre/include/lttng/error-query.h 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/include/lttng/error-query.h 2021-06-17 15:47:40.000000000 +0000 @@ -61,6 +61,10 @@ extern struct lttng_error_query *lttng_error_query_trigger_create( const struct lttng_trigger *trigger); +/* Create an error query targetting a trigger's condition object. */ +extern struct lttng_error_query *lttng_error_query_condition_create( + const struct lttng_trigger *trigger); + /* * Create an error query targetting an action object. * diff -Nru ltt-control-2.13~pre/include/lttng/error-query-internal.h ltt-control-2.13~pre/include/lttng/error-query-internal.h --- ltt-control-2.13~pre/include/lttng/error-query-internal.h 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/include/lttng/error-query-internal.h 2021-06-17 15:47:40.000000000 +0000 @@ -17,6 +17,7 @@ enum lttng_error_query_target_type { LTTNG_ERROR_QUERY_TARGET_TYPE_TRIGGER, + LTTNG_ERROR_QUERY_TARGET_TYPE_CONDITION, LTTNG_ERROR_QUERY_TARGET_TYPE_ACTION, }; @@ -29,6 +30,10 @@ const struct lttng_error_query *query); LTTNG_HIDDEN +const struct lttng_trigger *lttng_error_query_condition_borrow_target( + const struct lttng_error_query *query); + +LTTNG_HIDDEN const struct lttng_trigger *lttng_error_query_action_borrow_trigger_target( const struct lttng_error_query *query); diff -Nru ltt-control-2.13~pre/include/lttng/rotate-internal.h ltt-control-2.13~pre/include/lttng/rotate-internal.h --- ltt-control-2.13~pre/include/lttng/rotate-internal.h 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/include/lttng/rotate-internal.h 2021-06-17 15:47:40.000000000 +0000 @@ -108,11 +108,11 @@ struct { uint8_t set; uint64_t value; - } periodic; + } LTTNG_PACKED periodic; struct { uint8_t set; uint64_t value; - } size; + } LTTNG_PACKED size; } LTTNG_PACKED; #endif /* LTTNG_ROTATE_INTERNAL_ABI_H */ diff -Nru ltt-control-2.13~pre/include/lttng/trigger/trigger-internal.h ltt-control-2.13~pre/include/lttng/trigger/trigger-internal.h --- ltt-control-2.13~pre/include/lttng/trigger/trigger-internal.h 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/include/lttng/trigger/trigger-internal.h 2021-06-17 15:47:40.000000000 +0000 @@ -238,6 +238,11 @@ struct lttng_error_query_results *results); LTTNG_HIDDEN +enum lttng_trigger_status lttng_trigger_condition_add_error_results( + const struct lttng_trigger *trigger, + struct lttng_error_query_results *results); + +LTTNG_HIDDEN enum lttng_trigger_status lttng_trigger_add_action_error_query_results( struct lttng_trigger *trigger, struct lttng_error_query_results *results); diff -Nru ltt-control-2.13~pre/src/bin/lttng/commands/list.c ltt-control-2.13~pre/src/bin/lttng/commands/list.c --- ltt-control-2.13~pre/src/bin/lttng/commands/list.c 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/src/bin/lttng/commands/list.c 2021-06-17 15:47:40.000000000 +0000 @@ -2128,19 +2128,19 @@ } else { /* Pretty print */ if (count == 0) { - MSG("Currently no available tracing session"); + MSG("Currently no available recording session"); goto end; } if (session_name == NULL) { - MSG("Available tracing sessions:"); + MSG("Available recording sessions:"); } for (i = 0; i < count; i++) { if (session_name != NULL) { if (strncmp(sessions[i].name, session_name, NAME_MAX) == 0) { session_found = 1; - MSG("Tracing session %s: [%s%s]", session_name, + MSG("Recording session %s: [%s%s]", session_name, active_string(sessions[i].enabled), snapshot_string(sessions[i].snapshot_mode)); if (*sessions[i].path) { diff -Nru ltt-control-2.13~pre/src/bin/lttng/commands/list_triggers.c ltt-control-2.13~pre/src/bin/lttng/commands/list_triggers.c --- ltt-control-2.13~pre/src/bin/lttng/commands/list_triggers.c 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/src/bin/lttng/commands/list_triggers.c 2021-06-17 15:47:40.000000000 +0000 @@ -29,6 +29,8 @@ ; #endif +#define INDENTATION_LEVEL_STR " " + typedef enum lttng_event_rule_status (*event_rule_logging_get_name_pattern)( const struct lttng_event_rule *rule, const char **pattern); typedef enum lttng_event_rule_status (*event_rule_logging_get_filter)( @@ -638,6 +640,79 @@ } } +static +void print_indentation(unsigned int indentation_level) +{ + unsigned int i; + + for (i = 0; i < indentation_level; i++) { + _MSG(INDENTATION_LEVEL_STR); + } +} + +static +void print_error_query_results(struct lttng_error_query_results *results, + unsigned int base_indentation_level) +{ + unsigned int i, count, printed_errors_count = 0; + enum lttng_error_query_results_status results_status; + + results_status = lttng_error_query_results_get_count(results, &count); + assert(results_status == LTTNG_ERROR_QUERY_RESULTS_STATUS_OK); + + assert(results); + + print_indentation(base_indentation_level); + _MSG("errors:"); + + for (i = 0; i < count; i++) { + const struct lttng_error_query_result *result; + enum lttng_error_query_result_status result_status; + const char *result_name; + const char *result_description; + uint64_t result_value; + + results_status = lttng_error_query_results_get_result( + results, &result, i); + assert(results_status == LTTNG_ERROR_QUERY_RESULTS_STATUS_OK); + + result_status = lttng_error_query_result_get_name( + result, &result_name); + assert(result_status == LTTNG_ERROR_QUERY_RESULT_STATUS_OK); + result_status = lttng_error_query_result_get_description( + result, &result_description); + assert(result_status == LTTNG_ERROR_QUERY_RESULT_STATUS_OK); + + + if (lttng_error_query_result_get_type(result) == + LTTNG_ERROR_QUERY_RESULT_TYPE_COUNTER) { + result_status = lttng_error_query_result_counter_get_value( + result, &result_value); + assert(result_status == + LTTNG_ERROR_QUERY_RESULT_STATUS_OK); + if (result_value == 0) { + continue; + } + + MSG(""); + print_indentation(base_indentation_level + 1); + + _MSG("%s: %" PRIu64, result_name, result_value); + printed_errors_count++; + } else { + MSG(""); + print_indentation(base_indentation_level + 1); + _MSG("Unknown error query result type for result '%s' (%s)", + result_name, result_description); + continue; + } + } + + if (printed_errors_count == 0) { + _MSG(" none"); + } +} + static void print_condition_event_rule_matches( const struct lttng_condition *condition) { @@ -676,9 +751,7 @@ const uint64_t *action_path_indexes, size_t action_path_length) { - unsigned int i, count, printed_errors_count = 0; enum lttng_error_code error_query_ret; - enum lttng_error_query_results_status results_status; struct lttng_error_query_results *results = NULL; const char *trigger_name; uid_t trigger_uid; @@ -710,53 +783,7 @@ goto end; } - results_status = lttng_error_query_results_get_count(results, &count); - assert(results_status == LTTNG_ERROR_QUERY_RESULTS_STATUS_OK); - - _MSG(" errors:"); - - for (i = 0; i < count; i++) { - const struct lttng_error_query_result *result; - enum lttng_error_query_result_status result_status; - const char *result_name; - const char *result_description; - uint64_t result_value; - - results_status = lttng_error_query_results_get_result( - results, &result, i); - assert(results_status == LTTNG_ERROR_QUERY_RESULTS_STATUS_OK); - - result_status = lttng_error_query_result_get_name( - result, &result_name); - assert(result_status == LTTNG_ERROR_QUERY_RESULT_STATUS_OK); - result_status = lttng_error_query_result_get_description( - result, &result_description); - assert(result_status == LTTNG_ERROR_QUERY_RESULT_STATUS_OK); - - if (lttng_error_query_result_get_type(result) == - LTTNG_ERROR_QUERY_RESULT_TYPE_COUNTER) { - result_status = lttng_error_query_result_counter_get_value( - result, &result_value); - assert(result_status == - LTTNG_ERROR_QUERY_RESULT_STATUS_OK); - if (result_value == 0) { - continue; - } - - MSG(""); - _MSG(" %s: %" PRIu64, result_name, - result_value); - printed_errors_count++; - } else { - _MSG(" Unknown error query result type for result '%s' (%s)", - result_name, result_description); - continue; - } - } - - if (printed_errors_count == 0) { - _MSG(" none"); - } + print_error_query_results(results, 3); end: MSG(""); @@ -945,9 +972,7 @@ static void print_trigger_errors(const struct lttng_trigger *trigger) { - unsigned int i, count, printed_errors_count = 0; enum lttng_error_code error_query_ret; - enum lttng_error_query_results_status results_status; struct lttng_error_query_results *results = NULL; enum lttng_trigger_status trigger_status; const char *trigger_name; @@ -974,53 +999,45 @@ goto end; } - results_status = lttng_error_query_results_get_count(results, &count); - assert(results_status == LTTNG_ERROR_QUERY_RESULTS_STATUS_OK); - - _MSG(" errors:"); + print_error_query_results(results, 1); - for (i = 0; i < count; i++) { - const struct lttng_error_query_result *result; - enum lttng_error_query_result_status result_status; - const char *result_name; - const char *result_description; - uint64_t result_value; +end: + MSG(""); + lttng_error_query_destroy(query); + lttng_error_query_results_destroy(results); +} - results_status = lttng_error_query_results_get_result( - results, &result, i); - assert(results_status == LTTNG_ERROR_QUERY_RESULTS_STATUS_OK); +static +void print_condition_errors(const struct lttng_trigger *trigger) +{ + enum lttng_error_code error_query_ret; + struct lttng_error_query_results *results = NULL; + enum lttng_trigger_status trigger_status; + const char *trigger_name; + uid_t trigger_uid; + struct lttng_error_query *query = + lttng_error_query_condition_create(trigger); - result_status = lttng_error_query_result_get_name( - result, &result_name); - assert(result_status == LTTNG_ERROR_QUERY_RESULT_STATUS_OK); - result_status = lttng_error_query_result_get_description( - result, &result_description); - assert(result_status == LTTNG_ERROR_QUERY_RESULT_STATUS_OK); + assert(query); + /* + * Anonymous triggers are not listed; this would be an internal error. + */ + trigger_status = lttng_trigger_get_name(trigger, &trigger_name); + assert(trigger_status == LTTNG_TRIGGER_STATUS_OK); - if (lttng_error_query_result_get_type(result) == - LTTNG_ERROR_QUERY_RESULT_TYPE_COUNTER) { - result_status = lttng_error_query_result_counter_get_value( - result, &result_value); - assert(result_status == - LTTNG_ERROR_QUERY_RESULT_STATUS_OK); - if (result_value == 0) { - continue; - } + trigger_status = lttng_trigger_get_owner_uid(trigger, &trigger_uid); + assert(trigger_status == LTTNG_TRIGGER_STATUS_OK); - MSG(""); - _MSG(" %s: %" PRIu64, result_name, - result_value); - printed_errors_count++; - } else { - _MSG(" Unknown error query result type for result '%s' (%s)", - result_name, result_description); - continue; - } + error_query_ret = lttng_error_query_execute( + query, lttng_session_daemon_command_endpoint, &results); + if (error_query_ret != LTTNG_OK) { + ERR("Failed to query errors of condition of trigger '%s' (owner uid: %d): %s", + trigger_name, (int) trigger_uid, + lttng_strerror(-error_query_ret)); + goto end; } - if (printed_errors_count == 0) { - _MSG(" none"); - } + print_error_query_results(results, 2); end: MSG(""); @@ -1078,6 +1095,8 @@ abort(); } + print_condition_errors(trigger); + action = lttng_trigger_get_const_action(trigger); action_type = lttng_action_get_type(action); if (action_type == LTTNG_ACTION_TYPE_LIST) { diff -Nru ltt-control-2.13~pre/src/bin/lttng/lttng.c ltt-control-2.13~pre/src/bin/lttng/lttng.c --- ltt-control-2.13~pre/src/bin/lttng/lttng.c 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/src/bin/lttng/lttng.c 2021-06-17 15:47:40.000000000 +0000 @@ -272,7 +272,7 @@ puts(""); puts("Available commands:"); puts(""); - puts("Tracing sessions:"); + puts("Recording sessions:"); puts(" create " CONFIG_CMD_DESCR_CREATE); puts(" clear " CONFIG_CMD_DESCR_CLEAR); puts(" destroy " CONFIG_CMD_DESCR_DESTROY); @@ -299,7 +299,7 @@ puts(" start " CONFIG_CMD_DESCR_START); puts(" stop " CONFIG_CMD_DESCR_STOP); puts(""); - puts("Tracing session rotation:"); + puts("Recording session rotation:"); puts(" disable-rotation " CONFIG_CMD_DESCR_DISABLE_ROTATION); puts(" enable-rotation " CONFIG_CMD_DESCR_ENABLE_ROTATION); puts(" rotate " CONFIG_CMD_DESCR_ROTATE); diff -Nru ltt-control-2.13~pre/src/bin/lttng-sessiond/action-executor.c ltt-control-2.13~pre/src/bin/lttng-sessiond/action-executor.c --- ltt-control-2.13~pre/src/bin/lttng-sessiond/action-executor.c 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/src/bin/lttng-sessiond/action-executor.c 2021-06-17 15:47:40.000000000 +0000 @@ -748,7 +748,7 @@ DBG("Entering work execution loop"); pthread_mutex_lock(&executor->work.lock); while (!executor->should_quit) { - int ret; + int ret = 0; struct action_work_item *work_item; health_code_update(); @@ -983,7 +983,7 @@ static int add_action_to_subitem_array(struct lttng_action *action, struct lttng_dynamic_array *subitems) { - int ret; + int ret = 0; enum lttng_action_type type = lttng_action_get_type(action); const char *session_name = NULL; enum lttng_action_status status; diff -Nru ltt-control-2.13~pre/src/bin/lttng-sessiond/cmd.c ltt-control-2.13~pre/src/bin/lttng-sessiond/cmd.c --- ltt-control-2.13~pre/src/bin/lttng-sessiond/cmd.c 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/src/bin/lttng-sessiond/cmd.c 2021-06-17 15:47:40.000000000 +0000 @@ -4662,7 +4662,7 @@ { enum lttng_error_code ret_code; const struct lttng_trigger *query_target_trigger; - struct lttng_action *query_target_action = NULL; + const struct lttng_action *query_target_action = NULL; struct lttng_trigger *matching_trigger = NULL; const char *trigger_name; uid_t trigger_owner; @@ -4673,6 +4673,10 @@ case LTTNG_ERROR_QUERY_TARGET_TYPE_TRIGGER: query_target_trigger = lttng_error_query_trigger_borrow_target(query); break; + case LTTNG_ERROR_QUERY_TARGET_TYPE_CONDITION: + query_target_trigger = + lttng_error_query_condition_borrow_target(query); + break; case LTTNG_ERROR_QUERY_TARGET_TYPE_ACTION: query_target_trigger = lttng_error_query_action_borrow_trigger_target( query); @@ -4748,6 +4752,21 @@ } break; + case LTTNG_ERROR_QUERY_TARGET_TYPE_CONDITION: + { + trigger_status = lttng_trigger_condition_add_error_results( + matching_trigger, results); + + switch (trigger_status) { + case LTTNG_TRIGGER_STATUS_OK: + break; + default: + ret_code = LTTNG_ERR_UNK; + goto end; + } + + break; + } case LTTNG_ERROR_QUERY_TARGET_TYPE_ACTION: { const enum lttng_action_status action_status = diff -Nru ltt-control-2.13~pre/src/bin/lttng-sessiond/trigger-error-query.c ltt-control-2.13~pre/src/bin/lttng-sessiond/trigger-error-query.c --- ltt-control-2.13~pre/src/bin/lttng-sessiond/trigger-error-query.c 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/src/bin/lttng-sessiond/trigger-error-query.c 2021-06-17 15:47:40.000000000 +0000 @@ -15,6 +15,14 @@ const struct lttng_trigger *trigger, struct lttng_error_query_results *results) { + return LTTNG_TRIGGER_STATUS_OK; +} + +LTTNG_HIDDEN +enum lttng_trigger_status lttng_trigger_condition_add_error_results( + const struct lttng_trigger *trigger, + struct lttng_error_query_results *results) +{ enum lttng_trigger_status status; uint64_t discarded_tracer_messages_count; enum event_notifier_error_accounting_status error_accounting_status; @@ -29,7 +37,12 @@ &trigger_owner); assert(status == LTTNG_TRIGGER_STATUS_OK); - /* Only add discarded tracer messages count for applicable triggers. */ + /* + * Only add discarded tracer messages count for applicable conditions. + * As of 2.13, only "event rule matches" conditions can generate + * reportable errors hence why this function is very specific to this + * condition type. + */ if (!lttng_trigger_needs_tracer_notifier(trigger)) { status = LTTNG_TRIGGER_STATUS_OK; goto end; diff -Nru ltt-control-2.13~pre/src/common/error.c ltt-control-2.13~pre/src/common/error.c --- ltt-control-2.13~pre/src/common/error.c 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/src/common/error.c 2021-06-17 15:47:40.000000000 +0000 @@ -161,7 +161,7 @@ [ ERROR_INDEX(LTTNG_ERR_FILTER_INVAL) ] = "Invalid filter bytecode", [ ERROR_INDEX(LTTNG_ERR_FILTER_NOMEM) ] = "Not enough memory for filter bytecode", [ ERROR_INDEX(LTTNG_ERR_FILTER_EXIST) ] = "Filter already exist", - [ ERROR_INDEX(LTTNG_ERR_NO_CONSUMER) ] = "Consumer not found for tracing session", + [ ERROR_INDEX(LTTNG_ERR_NO_CONSUMER) ] = "Consumer not found for recording session", [ ERROR_INDEX(LTTNG_ERR_NO_SESSIOND) ] = "No session daemon is available", [ ERROR_INDEX(LTTNG_ERR_SESSION_STARTED) ] = "Session is running", [ ERROR_INDEX(LTTNG_ERR_NOT_SUPPORTED) ] = "Operation not supported", @@ -195,7 +195,7 @@ [ ERROR_INDEX(LTTNG_ERR_OVERFLOW) ] = "Overflow occurred", [ ERROR_INDEX(LTTNG_ERR_SESSION_NOT_STARTED) ] = "Session not started", [ ERROR_INDEX(LTTNG_ERR_LIVE_SESSION) ] = "Live sessions are not supported", - [ ERROR_INDEX(LTTNG_ERR_PER_PID_SESSION) ] = "Per-PID tracing sessions are not supported", + [ ERROR_INDEX(LTTNG_ERR_PER_PID_SESSION) ] = "Per-PID recording sessions are not supported", [ ERROR_INDEX(LTTNG_ERR_KERN_CONTEXT_UNAVAILABLE) ] = "Context unavailable on this kernel", [ ERROR_INDEX(LTTNG_ERR_REGEN_STATEDUMP_FAIL) ] = "Failed to regenerate the state dump", [ ERROR_INDEX(LTTNG_ERR_REGEN_STATEDUMP_NOMEM) ] = "Failed to regenerate the state dump, not enough memory", @@ -223,7 +223,7 @@ [ ERROR_INDEX(LTTNG_ERR_MKDIR_FAIL_CONSUMER) ] = "Directory creation failure on consumer", [ ERROR_INDEX(LTTNG_ERR_CHAN_NOT_FOUND) ] = "Channel not found", [ ERROR_INDEX(LTTNG_ERR_SNAPSHOT_UNSUPPORTED) ] = "Session configuration does not allow the use of snapshots", - [ ERROR_INDEX(LTTNG_ERR_SESSION_NOT_EXIST) ] = "Tracing session does not exist", + [ ERROR_INDEX(LTTNG_ERR_SESSION_NOT_EXIST) ] = "Recording session does not exist", [ ERROR_INDEX(LTTNG_ERR_CREATE_TRACE_CHUNK_FAIL_CONSUMER) ] = "Trace chunk creation failed on consumer", [ ERROR_INDEX(LTTNG_ERR_CLOSE_TRACE_CHUNK_FAIL_CONSUMER) ] = "Trace chunk close failed on consumer", [ ERROR_INDEX(LTTNG_ERR_TRACE_CHUNK_EXISTS_FAIL_CONSUMER) ] = "Failed to query consumer for trace chunk existence", diff -Nru ltt-control-2.13~pre/src/common/error-query.c ltt-control-2.13~pre/src/common/error-query.c --- ltt-control-2.13~pre/src/common/error-query.c 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/src/common/error-query.c 2021-06-17 15:47:40.000000000 +0000 @@ -36,6 +36,12 @@ struct lttng_trigger *trigger; }; +struct lttng_error_query_condition { + struct lttng_error_query parent; + /* Mutable only because of the reference count. */ + struct lttng_trigger *trigger; +}; + struct lttng_error_query_action { struct lttng_error_query parent; /* Mutable only because of the reference count. */ @@ -111,6 +117,37 @@ return query ? &query->parent : NULL; } +struct lttng_error_query *lttng_error_query_condition_create( + const struct lttng_trigger *trigger) +{ + struct lttng_error_query_condition *query = NULL; + struct lttng_trigger *trigger_copy = NULL; + + if (!trigger) { + goto end; + } + + trigger_copy = lttng_trigger_copy(trigger); + if (!trigger_copy) { + goto end; + } + + query = zmalloc(sizeof(*query)); + if (!query) { + PERROR("Failed to allocate condition error query"); + goto error; + } + + query->parent.target_type = LTTNG_ERROR_QUERY_TARGET_TYPE_CONDITION; + query->trigger = trigger_copy; + trigger_copy = NULL; + +error: + lttng_trigger_put(trigger_copy); +end: + return query ? &query->parent : NULL; +} + static struct lttng_action *get_trigger_action_from_path( struct lttng_trigger *trigger, @@ -606,6 +643,28 @@ } static +int lttng_error_query_condition_serialize(const struct lttng_error_query *query, + struct lttng_payload *payload) +{ + int ret; + const struct lttng_error_query_condition *query_trigger = + container_of(query, typeof(*query_trigger), parent); + + if (!lttng_trigger_validate(query_trigger->trigger)) { + ret = -1; + goto end; + } + + ret = lttng_trigger_serialize(query_trigger->trigger, payload); + if (ret) { + goto end; + } + +end: + return ret; +} + +static int lttng_error_query_action_serialize(const struct lttng_error_query *query, struct lttng_payload *payload) { @@ -650,6 +709,16 @@ } LTTNG_HIDDEN +const struct lttng_trigger *lttng_error_query_condition_borrow_target( + const struct lttng_error_query *query) +{ + const struct lttng_error_query_condition *query_trigger = + container_of(query, typeof(*query_trigger), parent); + + return query_trigger->trigger; +} + +LTTNG_HIDDEN const struct lttng_trigger *lttng_error_query_action_borrow_trigger_target( const struct lttng_error_query *query) { @@ -676,7 +745,7 @@ struct lttng_payload *payload) { int ret; - struct lttng_error_query_comm header = { + const struct lttng_error_query_comm header = { .target_type = (typeof(header.target_type)) query->target_type, }; @@ -695,6 +764,13 @@ } break; + case LTTNG_ERROR_QUERY_TARGET_TYPE_CONDITION: + ret = lttng_error_query_condition_serialize(query, payload); + if (ret) { + goto end; + } + + break; case LTTNG_ERROR_QUERY_TARGET_TYPE_ACTION: ret = lttng_error_query_action_serialize(query, payload); if (ret) { @@ -754,6 +830,35 @@ if (!*query) { used_size = -1; goto end; + } + + break; + } + case LTTNG_ERROR_QUERY_TARGET_TYPE_CONDITION: + { + ssize_t trigger_used_size; + struct lttng_payload_view trigger_view = + lttng_payload_view_from_view( + view, used_size, -1); + + if (!lttng_payload_view_is_valid(&trigger_view)) { + used_size = -1; + goto end; + } + + trigger_used_size = lttng_trigger_create_from_payload( + &trigger_view, &trigger); + if (trigger_used_size < 0) { + used_size = -1; + goto end; + } + + used_size += trigger_used_size; + + *query = lttng_error_query_condition_create(trigger); + if (!*query) { + used_size = -1; + goto end; } break; diff -Nru ltt-control-2.13~pre/src/common/Makefile.am ltt-control-2.13~pre/src/common/Makefile.am --- ltt-control-2.13~pre/src/common/Makefile.am 2021-06-16 15:49:22.000000000 +0000 +++ ltt-control-2.13~pre/src/common/Makefile.am 2021-06-17 15:47:40.000000000 +0000 @@ -3,10 +3,14 @@ AUTOMAKE_OPTIONS = subdir-objects SUBDIRS = \ - string-utils \ + argpar \ bytecode \ + compat \ + config \ + fd-tracker \ + string-utils \ filter \ - argpar + hashtable # Make sure to always distribute all folders # since SUBDIRS is decided at configure time. @@ -120,18 +124,10 @@ $(top_builddir)/src/common/filter/libfilter.la \ $(top_builddir)/src/vendor/msgpack/libmsgpack.la -if BUILD_LIB_COMPAT -SUBDIRS += compat -endif - if BUILD_LIB_HEALTH SUBDIRS += health endif -if BUILD_LIB_HASHTABLE -SUBDIRS += hashtable -endif - if BUILD_LIB_KERNEL_CTL SUBDIRS += kernel-ctl endif @@ -144,9 +140,6 @@ SUBDIRS += relayd endif -if BUILD_LIB_FD_TRACKER -SUBDIRS += fd-tracker -endif if BUILD_LIB_KERNEL_CONSUMER SUBDIRS += kernel-consumer @@ -164,10 +157,6 @@ SUBDIRS += index endif -if BUILD_LIB_CONFIG -SUBDIRS += config -endif - if BUILD_LIB_CONSUMER SUBDIRS += consumer endif diff -Nru ltt-control-2.13~pre/src/lib/lttng-ctl/lttng-ctl.pc.in ltt-control-2.13~pre/src/lib/lttng-ctl/lttng-ctl.pc.in --- ltt-control-2.13~pre/src/lib/lttng-ctl/lttng-ctl.pc.in 2021-06-16 15:49:23.000000000 +0000 +++ ltt-control-2.13~pre/src/lib/lttng-ctl/lttng-ctl.pc.in 2021-06-17 15:47:40.000000000 +0000 @@ -9,7 +9,7 @@ includedir=@includedir@ Name: LTTng control library -Description: The LTTng control and utility library is a library used to control the tracing sessions of a LTTng-session daemon +Description: Control LTTng recording sessions and triggers Version: @PACKAGE_VERSION@ Requires: Requires.private: diff -Nru ltt-control-2.13~pre/tests/regression/tools/notification/test_notification_notifier_discarded_count ltt-control-2.13~pre/tests/regression/tools/notification/test_notification_notifier_discarded_count --- ltt-control-2.13~pre/tests/regression/tools/notification/test_notification_notifier_discarded_count 2021-06-16 15:49:23.000000000 +0000 +++ ltt-control-2.13~pre/tests/regression/tools/notification/test_notification_notifier_discarded_count 2021-06-17 15:47:40.000000000 +0000 @@ -41,13 +41,13 @@ "$FULL_LTTNG_BIN" list-triggers > "$list_triggers_stdout" - cat "$list_triggers_stdout" | grep -a7 "$trigger_name" | tail -1 | grep --quiet "errors: none" + cat "$list_triggers_stdout" | grep -A7 "$trigger_name" | grep -A2 "event rule matches" | tail -1 | grep --quiet "errors: none" ret=$? if [ "$ret" -eq "0" ]; then notif_nb="0" else - notif_nb=$(cat "$list_triggers_stdout" | grep -a8 "$trigger_name" | tail -1 | grep "discarded tracer messages" | cut -d' ' -f8) + notif_nb=$(cat "$list_triggers_stdout" | grep -A7 "$trigger_name" | grep "discarded tracer messages" | cut -d' ' -f10) fi rm -f "$list_triggers_stdout" diff -Nru ltt-control-2.13~pre/tests/regression/tools/trigger/start-stop/test_start_stop ltt-control-2.13~pre/tests/regression/tools/trigger/start-stop/test_start_stop --- ltt-control-2.13~pre/tests/regression/tools/trigger/start-stop/test_start_stop 2021-06-16 15:49:23.000000000 +0000 +++ ltt-control-2.13~pre/tests/regression/tools/trigger/start-stop/test_start_stop 2021-06-17 15:47:40.000000000 +0000 @@ -25,7 +25,7 @@ function lttng_session_is_active() { local SESSION_NAME="$1" - "$FULL_LTTNG_BIN" list "$SESSION_NAME" | grep "Tracing session" | grep -q "\[active\]" + "$FULL_LTTNG_BIN" list "$SESSION_NAME" | grep "Recording session" | grep -q "\[active\]" ok $ret "Session \"$SESSION_NAME\" is active" } @@ -33,7 +33,7 @@ function lttng_session_is_inactive() { local SESSION_NAME="$1" - "$FULL_LTTNG_BIN" list "$SESSION_NAME" | grep "Tracing session" | grep -q "\[inactive\]" + "$FULL_LTTNG_BIN" list "$SESSION_NAME" | grep "Recording session" | grep -q "\[inactive\]" ok $ret "Session \"$SESSION_NAME\" is inactive" } diff -Nru ltt-control-2.13~pre/tests/regression/tools/trigger/test_list_triggers_cli ltt-control-2.13~pre/tests/regression/tools/trigger/test_list_triggers_cli --- ltt-control-2.13~pre/tests/regression/tools/trigger/test_list_triggers_cli 2021-06-16 15:49:23.000000000 +0000 +++ ltt-control-2.13~pre/tests/regression/tools/trigger/test_list_triggers_cli 2021-06-17 15:47:40.000000000 +0000 @@ -62,6 +62,7 @@ owner uid: ${uid} condition: event rule matches rule: test-name (type: user tracepoint) + errors: none actions: notify errors: none @@ -93,6 +94,7 @@ owner uid: ${uid} condition: event rule matches rule: aaa (type: user tracepoint, filter: p == 2) + errors: none actions: notify errors: none @@ -101,6 +103,7 @@ owner uid: ${uid} condition: event rule matches rule: gerboise (type: user tracepoint, log level at least INFO) + errors: none actions: notify errors: none @@ -109,6 +112,7 @@ owner uid: ${uid} condition: event rule matches rule: * (type: user tracepoint) + errors: none actions: notify errors: none @@ -117,6 +121,7 @@ owner uid: ${uid} condition: event rule matches rule: hello* (type: user tracepoint, exclusions: hello2,hello3,hello4) + errors: none actions: notify errors: none @@ -125,6 +130,7 @@ owner uid: ${uid} condition: event rule matches rule: lemming (type: user tracepoint, log level is WARNING) + errors: none actions: notify errors: none @@ -135,6 +141,7 @@ rule: capture-payload-field (type: user tracepoint) captures: - a + errors: none actions: notify errors: none @@ -146,6 +153,7 @@ captures: - a[2] - \$ctx.tourlou[18] + errors: none actions: notify errors: none @@ -156,6 +164,7 @@ rule: capture-chan-ctx (type: user tracepoint) captures: - \$ctx.vpid + errors: none actions: notify errors: none @@ -166,6 +175,7 @@ rule: capture-app-ctx (type: user tracepoint) captures: - \$app.iga:active_clients + errors: none actions: notify errors: none @@ -174,6 +184,7 @@ owner uid: ${uid} condition: event rule matches rule: lemming (type: user tracepoint) + errors: none actions: notify errors: none @@ -226,6 +237,7 @@ owner uid: ${uid} condition: event rule matches rule: my_channel_enable (type: kernel:kprobe, location: lttng_channel_enable) + errors: none actions: notify errors: none @@ -234,6 +246,7 @@ owner uid: ${uid} condition: event rule matches rule: my_channel_enable (type: kernel:kprobe, location: ${base_symbol}+${offset_hex}) + errors: none actions: notify errors: none @@ -242,6 +255,7 @@ owner uid: ${uid} condition: event rule matches rule: my_channel_enable (type: kernel:kprobe, location: 0x${channel_enable_addr}) + errors: none actions: notify errors: none @@ -268,6 +282,7 @@ owner uid: ${uid} condition: event rule matches rule: ma-probe-elf (type: kernel:uprobe, location type: ELF, location: ${uprobe_elf_binary}:${elf_function_name}) + errors: none actions: notify errors: none @@ -293,6 +308,7 @@ owner uid: 0 condition: event rule matches rule: ma-probe-sdt (type: kernel:uprobe, location type: SDT, location: ${uprobe_sdt_binary}:${sdt_provider_name}:${sdt_probe_name}) + errors: none actions: notify errors: none @@ -319,6 +335,7 @@ owner uid: ${uid} condition: event rule matches rule: open (type: kernel:syscall:entry+exit) + errors: none actions: notify errors: none @@ -327,6 +344,7 @@ owner uid: ${uid} condition: event rule matches rule: open (type: kernel:syscall:entry) + errors: none actions: notify errors: none @@ -335,6 +353,7 @@ owner uid: ${uid} condition: event rule matches rule: open (type: kernel:syscall:exit) + errors: none actions: notify errors: none @@ -343,6 +362,7 @@ owner uid: ${uid} condition: event rule matches rule: open (type: kernel:syscall:entry+exit) + errors: none actions: notify errors: none @@ -351,6 +371,7 @@ owner uid: ${uid} condition: event rule matches rule: ptrace (type: kernel:syscall:entry+exit, filter: a > 2) + errors: none actions: notify errors: none @@ -376,6 +397,7 @@ condition: session consumed size session name: the-session-name threshold: 1234 bytes + errors: none actions: notify errors: none @@ -399,6 +421,7 @@ channel name: the-channel-name domain: ust threshold (bytes): 1234 + errors: none actions: notify errors: none @@ -410,6 +433,7 @@ channel name: the-channel-name domain: ust threshold (ratio): 0.25 + errors: none actions: notify errors: none @@ -421,6 +445,7 @@ channel name: the-channel-name domain: ust threshold (bytes): 2345 + errors: none actions: notify errors: none @@ -432,6 +457,7 @@ channel name: the-channel-name domain: ust threshold (ratio): 0.40 + errors: none actions: notify errors: none @@ -455,6 +481,7 @@ owner uid: ${uid} condition: session rotation completed session name: the-session-name + errors: none actions: notify errors: none @@ -463,6 +490,7 @@ owner uid: ${uid} condition: session rotation ongoing session name: the-session-name + errors: none actions: notify errors: none @@ -495,6 +523,7 @@ owner uid: ${uid} condition: event rule matches rule: some-event (type: user tracepoint) + errors: none actions: snapshot session \`ze-session\` errors: none @@ -503,6 +532,7 @@ owner uid: ${uid} condition: event rule matches rule: some-event (type: user tracepoint) + errors: none actions: snapshot session \`ze-session\`, path: /some/path errors: none @@ -511,6 +541,7 @@ owner uid: ${uid} condition: event rule matches rule: some-event (type: user tracepoint) + errors: none actions: snapshot session \`ze-session\`, path: /some/other/path errors: none @@ -519,6 +550,7 @@ owner uid: ${uid} condition: event rule matches rule: some-event (type: user tracepoint) + errors: none actions: snapshot session \`ze-session\`, url: net://1.2.3.4 errors: none @@ -527,6 +559,7 @@ owner uid: ${uid} condition: event rule matches rule: some-event (type: user tracepoint) + errors: none actions: snapshot session \`ze-session\`, url: net://1.2.3.4:1234:1235 errors: none @@ -535,6 +568,7 @@ owner uid: ${uid} condition: event rule matches rule: some-event (type: user tracepoint) + errors: none actions: snapshot session \`ze-session\`, control url: tcp://1.2.3.4:1111, data url: tcp://1.2.3.4:1112 errors: none @@ -543,6 +577,7 @@ owner uid: ${uid} condition: event rule matches rule: some-event (type: user tracepoint) + errors: none actions: snapshot session \`ze-session\`, path: /some/path, max size: 1234 errors: none @@ -551,6 +586,7 @@ owner uid: ${uid} condition: event rule matches rule: some-event (type: user tracepoint) + errors: none actions: snapshot session \`ze-session\`, path: /some/path, name: meh errors: none @@ -559,6 +595,7 @@ owner uid: ${uid} condition: event rule matches rule: some-event (type: user tracepoint) + errors: none actions: snapshot session \`ze-session\`, rate policy: every 10 occurrences errors: none @@ -567,6 +604,7 @@ owner uid: ${uid} condition: event rule matches rule: some-event (type: user tracepoint) + errors: none actions: snapshot session \`ze-session\`, rate policy: once after 10 occurrences errors: none @@ -597,6 +635,7 @@ owner uid: ${uid} condition: event rule matches rule: some-event (type: user tracepoint) + errors: none actions: notify, rate policy: once after 5 occurrences errors: none @@ -605,6 +644,7 @@ owner uid: ${uid} condition: event rule matches rule: some-event (type: user tracepoint) + errors: none actions: notify, rate policy: every 10 occurrences errors: none diff -Nru ltt-control-2.13~pre/tests/regression/tools/trigger/test_remove_trigger_cli ltt-control-2.13~pre/tests/regression/tools/trigger/test_remove_trigger_cli --- ltt-control-2.13~pre/tests/regression/tools/trigger/test_remove_trigger_cli 2021-06-16 15:49:23.000000000 +0000 +++ ltt-control-2.13~pre/tests/regression/tools/trigger/test_remove_trigger_cli 2021-06-17 15:47:40.000000000 +0000 @@ -76,6 +76,7 @@ owner uid: ${uid} condition: event rule matches rule: aaa (type: user tracepoint, filter: p == 2) + errors: none actions: notify errors: none @@ -84,6 +85,7 @@ owner uid: ${uid} condition: event rule matches rule: * (type: user tracepoint) + errors: none actions: notify errors: none @@ -98,6 +100,7 @@ owner uid: ${uid} condition: event rule matches rule: * (type: user tracepoint) + errors: none actions: notify errors: none diff -Nru ltt-control-2.13~pre/tests/regression/ust/python-logging/test_python_logging.in ltt-control-2.13~pre/tests/regression/ust/python-logging/test_python_logging.in --- ltt-control-2.13~pre/tests/regression/ust/python-logging/test_python_logging.in 2021-06-16 15:49:23.000000000 +0000 +++ ltt-control-2.13~pre/tests/regression/ust/python-logging/test_python_logging.in 2021-06-17 15:47:40.000000000 +0000 @@ -700,6 +700,7 @@ owner uid: ${uid} condition: event rule matches rule: * (type: python:logging) + errors: none actions: notify errors: none diff -Nru ltt-control-2.13~pre/tests/utils/test_utils.py ltt-control-2.13~pre/tests/utils/test_utils.py --- ltt-control-2.13~pre/tests/utils/test_utils.py 2021-06-16 15:49:23.000000000 +0000 +++ ltt-control-2.13~pre/tests/utils/test_utils.py 2021-06-17 15:47:40.000000000 +0000 @@ -74,7 +74,7 @@ res = create(session_name, trace_path) if res < 0: - bail("Failed to create tracing session.") + bail("Failed to create recording session.") channel = Channel() channel.name = "channel0"