X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;ds=sidebyside;f=man%2Fsystemd-analyze.xml;h=f5a94242480163b82741fb1954a88c0874b0054c;hb=a3f6aa268c7d40f67d4e0d427bc26aef773db8ec;hp=9f313d76f111a956e574ad7d8f80e63a4379ed19;hpb=816f25e86ab690da6e408bc8d5b03dae9cc1b219;p=elogind.git
diff --git a/man/systemd-analyze.xml b/man/systemd-analyze.xml
index 9f313d76f..f5a942424 100644
--- a/man/systemd-analyze.xml
+++ b/man/systemd-analyze.xml
@@ -34,6 +34,12 @@
Poetteringlennart@poettering.net
+
+ Developer
+ Harald
+ Hoyer
+ harald@redhat.com
+
@@ -49,16 +55,32 @@
- systemd-analyze OPTIONS time
+ systemd-analyze
+ OPTIONS
+ time
+
+
+ systemd-analyze
+ OPTIONS
+ blame
- systemd-analyze OPTIONS blame
+ systemd-analyze
+ OPTIONS
+ critical-chain
+ UNIT
- systemd-analyze OPTIONS plot > file.svg
+ systemd-analyze
+ OPTIONS
+ plot
+ > file.svg
- systemd-analyze OPTIONS dot pattern...
+ systemd-analyze
+ OPTIONS
+ dot
+ PATTERN
@@ -73,7 +95,7 @@
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
@@ -88,6 +110,18 @@
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
@@ -101,7 +135,7 @@
dot | dot -Tsvg > systemd.svg to generate a
graphical dependency tree. Unless
or
- is passed the generated graph will show both ordering
+ is passed, the generated graph will show both ordering
and requirement dependencies. Optional pattern
globbing style specifications
(e.g. *.target) may be given at
@@ -109,7 +143,7 @@
any of these patterns match either the origin or
destination node.
- If no command is passed systemd-analyze
+ If no command is passed, systemd-analyze
time is implied.
@@ -157,7 +191,7 @@
RequisiteOverridable=,
Wants= and
Conflicts= are
- shown. If neither is passed, shows
+ shown. If neither is passed, this shows
dependencies of all these
types.
@@ -169,18 +203,31 @@
When used in
conjunction with the
dot command (see
- above), selects which relationships
+ above), this 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
+ 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 given
+ 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".
+
@@ -196,7 +243,7 @@
ExamplesThis plots all dependencies of any unit whose
- name starts with "avahi-daemon.":
+ name starts with avahi-daemon.:
$ systemd-analyze dot 'avahi-daemon.*' | dot -Tsvg > avahi.svg
$ eog avahi.svg