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=c2ff9cc5bd23c5ffc3eb776bac1bcd57820a751d;hpb=ecbd4565c88f2a10422f74cff79e45a6f0edb6a2;p=elogind.git
diff --git a/man/systemd-analyze.xml b/man/systemd-analyze.xml
index c2ff9cc5b..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,9 +60,15 @@
systemd-analyze OPTIONS blame
+
+ systemd-analyze OPTIONS critical-chain
+ systemd-analyze OPTIONS plot > file.svg
+
+ systemd-analyze OPTIONS dot pattern...
+
@@ -85,11 +97,37 @@
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
+ 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.
+
If no command is passed systemd-analyze
time is implied.
@@ -116,6 +154,65 @@
of user sessions instead of the system
manager.
+
+
+
+
+
+ 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, shows
+ dependencies of all these
+ types.
+
+
+
+
+
+
+ When used in
+ conjunction with the
+ dot command (see
+ above), selects which relationships
+ are shown in the dependency graph.
+ They both require
+ glob7
+ patterns as arguments, which are
+ matched against lefthand and
+ righthand, respectively, nodes of a
+ relationship. Each of these can be
+ used more than once which means a
+ 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".
+
@@ -127,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