X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd-analyze.xml;h=ae45bfcf3150bf13d9cd9ddbd16173b4621187b3;hb=a0ab566574303be1ca12cdb334f284cfd407caa5;hp=c8d0b4743b743ba8d0fdefb0795039b2b07b5b50;hpb=e55933db18d1037876e7a0962bcf6ef6c0bbbd68;p=elogind.git
diff --git a/man/systemd-analyze.xml b/man/systemd-analyze.xml
index c8d0b4743..ae45bfcf3 100644
--- a/man/systemd-analyze.xml
+++ b/man/systemd-analyze.xml
@@ -34,6 +34,12 @@
Poetteringlennart@poettering.net
+
+ Developer
+ Harald
+ Hoyer
+ harald@redhat.com
+
@@ -54,6 +60,9 @@
systemd-analyze OPTIONS blame
+
+ systemd-analyze OPTIONS critical-chain
+ systemd-analyze OPTIONS plot > file.svg
@@ -88,25 +97,36 @@
be slow simply because it waits for the initialization
of another service to complete.
+ systemd-analyze critical-chain
+ prints a tree of the time critical chain of units.
+ 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.
- systemd-analyze dot
- Generate textual dependency graph description in dot
- format for further processing with the GraphViz
+ systemd-analyze dot Generate
+ 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
+ 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 patterns may be given at the end. The
- relationship is printed if any of these matches either
- lefthand or righthand node.
+ 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.If no command is passed systemd-analyze
time is implied.
@@ -180,6 +200,19 @@
unit name must match one of 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,
+ i.e. "50ms".
+
@@ -191,6 +224,23 @@
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-patter='*.target' | dot -Tsvg > targets.svg
+$ eog targets.svg
+
+
+
+
See Also