X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd-analyze.xml;h=c7a25985ca9a116299626f112bb57e36383895f8;hb=0138a2dcc50d261ea3512b0eaca2c6e9d4a807f0;hp=c2ff9cc5bd23c5ffc3eb776bac1bcd57820a751d;hpb=f274ece0f76b5709408821e317e87aef76123db6;p=elogind.git
diff --git a/man/systemd-analyze.xml b/man/systemd-analyze.xml
index c2ff9cc5b..c7a25985c 100644
--- a/man/systemd-analyze.xml
+++ b/man/systemd-analyze.xml
@@ -21,7 +21,8 @@
along with systemd; If not, see .
-->
-
+systemd-analyze
@@ -34,6 +35,12 @@
Poetteringlennart@poettering.net
+
+ Developer
+ Harald
+ Hoyer
+ harald@redhat.com
+
@@ -49,13 +56,44 @@
- systemd-analyze OPTIONS time
+ systemd-analyze
+ OPTIONS
+ time
+
+
+ systemd-analyze
+ OPTIONS
+ blame
+
+
+ systemd-analyze
+ OPTIONS
+ critical-chain
+ UNIT
+
+
+ systemd-analyze
+ OPTIONS
+ plot
+ > file.svg
- systemd-analyze OPTIONS blame
+ systemd-analyze
+ OPTIONS
+ dot
+ PATTERN
+ > file.dot
- systemd-analyze OPTIONS plot > file.svg
+ systemd-analyze
+ OPTIONS
+ dump
+
+
+ systemd-analyze
+ OPTIONS
+ set-log-level
+ LEVEL
@@ -63,14 +101,15 @@
Descriptionsystemd-analyze may be used
- to determine system boot-up performance of the current
- boot.
+ to determine system boot-up performance statistics and
+ retrieve other state and tracing information from the
+ system and service manager.
systemd-analyze time
prints the time spent in the kernel before
userspace has been reached, the time spent in the
initial RAM disk (initrd) before normal system
- userspace has been reached and the time normal system
+ userspace has been reached, and the time normal system
userspace took to initialize. Note that these
measurements simply measure the time passed up to the
point where all system services have been spawned, but
@@ -85,12 +124,54 @@
be slow simply because it waits for the initialization
of another service to complete.
+ systemd-analyze critical-chain [UNIT...]
+ prints a tree of the time-critical chain of units
+ (for each of the specified UNITs
+ or for the default target otherwise).
+ The time after the unit is active or started is printed
+ after the "@" character. The time the unit takes to
+ start is printed after the "+" character.
+ Note that the output might be misleading as the
+ initialization of one service might depend on socket
+ activation and because of the parallel execution
+ of units.
+
systemd-analyze plot prints
an SVG graphic detailing which system services have
been started at what time, highlighting the time they
spent on initialization.
- If no command is passed systemd-analyze
+ systemd-analyze dot generates
+ textual dependency graph description in dot format for
+ further processing with the GraphViz
+ dot1
+ tool. Use a command line like systemd-analyze
+ dot | dot -Tsvg > systemd.svg to generate a
+ graphical dependency tree. Unless
+ or
+ is passed, the generated graph will show both ordering
+ and requirement dependencies. Optional pattern
+ globbing style specifications
+ (e.g. *.target) may be given at
+ the end. A unit dependency is included in the graph if
+ any of these patterns match either the origin or
+ destination node.
+
+ systemd-analyze dump outputs
+ a (usually very long) human-readable serialization of
+ the complete server state. Its format is subject to
+ change without notice and should not be parsed by
+ applications.
+
+ systemd-analyze set-log-level
+ LEVEL changes the
+ current log level of the systemd
+ daemon to LEVEL (accepts
+ the same values as
+ described in
+ systemd1).
+
+ If no command is passed, systemd-analyze
time is implied.
@@ -102,20 +183,86 @@
-
-
+
- Prints a short help
- text and exits.
+ Shows performance data
+ of user sessions instead of the system
+ manager.
-
+ Shows performance data
- of user sessions instead of the system
- manager.
+ of the system manager. This is the
+ implied default.
+
+
+
+
+
+
+ When used in
+ conjunction with the
+ dot command (see
+ above), selects which dependencies are
+ shown in the dependency graph. If
+ is passed,
+ only dependencies of type
+ After= or
+ Before= are
+ shown. If
+ is passed, only dependencies of type
+ Requires=,
+ RequiresOverridable=,
+ Requisite=,
+ RequisiteOverridable=,
+ Wants= and
+ Conflicts= are
+ shown. If neither is passed, this shows
+ dependencies of all these
+ types.
+
+
+
+
+
+
+ When used in
+ conjunction with the
+ dot command (see
+ above), this selects which relationships
+ are shown in the dependency graph.
+ They both require
+ glob7
+ patterns as arguments, which are
+ matched against left-hand and
+ right-hand, respectively, nodes of a
+ relationship. Each of these can be
+ used more than once, which means a
+ unit name must match one of the given
+ values.
+
+
+
+ timespan
+
+ When used in conjunction
+ with the critical-chain
+ command (see above), also show units, which
+ finished timespan earlier, than the
+ latest unit in the same level. The unit of
+ timespan is seconds
+ unless specified with a different unit,
+ e.g. "50ms".
+
+
+
+
+
+
+
@@ -123,10 +270,29 @@
Exit status
- On success 0 is returned, a non-zero failure
+ On success, 0 is returned, a non-zero failure
code otherwise.
+
+ Examples
+
+ This plots all dependencies of any unit whose
+ name starts with avahi-daemon.:
+
+ $ systemd-analyze dot 'avahi-daemon.*' | dot -Tsvg > avahi.svg
+$ eog avahi.svg
+
+ This plots the dependencies between all known target units:
+
+ systemd-analyze dot --to-pattern='*.target' --from-pattern='*.target' | dot -Tsvg > targets.svg
+$ eog targets.svg
+
+
+
+
+
+
See Also