Fix: lttng-ctl: lttng_list_sessions: initialize out_sessions to NULL when returning 0
[lttng-tools.git] / doc / man / lttng-regenerate.1.txt
... / ...
CommitLineData
1lttng-regenerate(1)
2===================
3:revdate: 14 June 2021
4
5
6NAME
7----
8lttng-regenerate - Regenerate specific data of an LTTng recording session
9
10
11SYNOPSIS
12--------
13Regenerate the metadata of a recording session:
14
15[verse]
16*lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *regenerate metadata* [option:--session='SESSION']
17
18Regenerate the state dump event records of a recording session:
19
20[verse]
21*lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *regenerate statedump* [option:--session='SESSION']
22
23
24DESCRIPTION
25-----------
26The `lttng regenerate` command regenerates specific data of:
27
28With the option:--session='SESSION' option::
29 The recording session named 'SESSION'.
30
31Without the option:--session option::
32 The current recording session (see man:lttng-concepts(7) to learn
33 more about the current recording session).
34
35See man:lttng-concepts(7) to learn more about recording sessions.
36
37As of this version, the `metadata` and `statedump` targets are
38available.
39
40See the ``<<examples,EXAMPLES>>'' section below for usage examples.
41
42
43Regenerate the metadata of a recording session
44~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
45Use the `metadata` target to resample the offset between the monotonic
46clock and the wall time of the system, and then regenerate the metadata
47stream files.
48
49More specifically, you may want to resample the wall time following a
50major link:https://en.wikipedia.org/wiki/Network_Time_Protocol[NTP]
51correction. As such, LTTng can trace a system booting with an incorrect
52wall time before its wall time is NTP-corrected. Regenerating the
53metadata of the selected recording session ensures that trace readers
54can accurately determine the event record timestamps relative to the
55Unix epoch.
56
57Note that if you plan to rotate (see man:lttng-concepts(7) to learn
58more) the selected recording session, this target only regenerates the
59metadata stream files of the current and next trace chunks.
60
61[IMPORTANT]
62====
63You can only use the `metadata` target when the selected
64recording session:
65
66* Is not in live mode (nloption:--live option of
67 man:lttng-create(1)).
68
69* If it has user space channels, they're configured to use a
70 per-user buffering scheme (nloption:--buffers-uid option of
71 man:lttng-enable-channel(1)).
72+
73See man:lttng-concepts(7) to learn more about channels.
74====
75
76
77Regenerate the state dump event records of a recording session
78~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
79Use the `statedump` target to collect up-to-date state dump information
80and create corresponding event records.
81
82This is particularly useful if the selected recording session is in
83snapshot mode (nloption:--snapshot option of the man:lttng-create(1)
84command) or if LTTng rotates trace files for one of its channels (see
85man:lttng-concepts(7)): in both cases, the state dump information may be
86lost.
87
88
89include::common-lttng-cmd-options-head.txt[]
90
91
92option:-s 'SESSION', option:--session='SESSION'::
93 Regenerate specific data of the recording session named 'SESSION'
94 instead of the current recording session.
95
96
97include::common-lttng-cmd-help-options.txt[]
98
99
100include::common-lttng-cmd-after-options.txt[]
101
102
103[[examples]]
104EXAMPLES
105--------
106.Regenerate the metadata of the current recording session.
107====
108[role="term"]
109----
110$ lttng regenerate metadata
111----
112====
113
114.Regenerate the state dump event records of a specific recording session.
115====
116See the option:--session option.
117
118[role="term"]
119----
120$ lttng regenerate statedump --session=my-session
121----
122====
123
124
125include::common-footer.txt[]
126
127
128SEE ALSO
129--------
130man:lttng(1),
131man:lttng-concepts(7)
This page took 0.02373 seconds and 4 git commands to generate.