X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;ds=sidebyside;f=man%2Fsystemd-analyze.xml;h=073e807b416097b2adc4d005530dc14086d4187c;hb=92ff080be100aff15f292e2631921131c610afe7;hp=ae45bfcf3150bf13d9cd9ddbd16173b4621187b3;hpb=bb150966c0687d2fa94da0a36dabba90c1a84b8b;p=elogind.git
diff --git a/man/systemd-analyze.xml b/man/systemd-analyze.xml
index ae45bfcf3..073e807b4 100644
--- a/man/systemd-analyze.xml
+++ b/man/systemd-analyze.xml
@@ -21,7 +21,8 @@
along with systemd; If not, see .
-->
-
+systemd-analyze
@@ -55,19 +56,50 @@
- systemd-analyze OPTIONS time
+ systemd-analyze
+ OPTIONS
+ time
- systemd-analyze OPTIONS blame
+ systemd-analyze
+ OPTIONS
+ blame
- systemd-analyze OPTIONS critical-chain
+ 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
+ > file.dot
+
+
+ systemd-analyze
+ OPTIONS
+ dump
+
+
+ systemd-analyze
+ OPTIONS
+ set-log-level
+ LEVEL
+
+
+ systemd-analyze
+ OPTIONS
+ verify
+ FILES
@@ -75,14 +107,16 @@
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, and to verify the
+ correctness of unit files.
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
@@ -97,8 +131,10 @@
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.
+ 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.
@@ -112,7 +148,7 @@
been started at what time, highlighting the time they
spent on initialization.
- systemd-analyze dot Generate
+ systemd-analyze dot generates
textual dependency graph description in dot format for
further processing with the GraphViz
dot1
@@ -120,7 +156,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
@@ -128,7 +164,32 @@
any of these patterns match either the origin or
destination node.
- If no command is passed systemd-analyze
+ 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).
+
+ systemd-analyze verify will
+ load unit files and print warnings if any errors are
+ detected. Files specified on the command line will be
+ loaded, but also any other units referenced by
+ them. This command works by prepending the directories
+ for all command line arguments at the beginning of the
+ unit load path, which means that all units files found
+ in those directories will be used in preference to the
+ unit files found in the standard locations, even if
+ not listed explicitly.
+
+ If no command is passed, systemd-analyze
time is implied.
@@ -140,19 +201,18 @@
-
-
+
- Prints a short help
- text and exits.
+ Operates on the user
+ systemd instance.
-
+
- Shows performance data
- of user sessions instead of the system
- manager.
+ Operates on the system
+ systemd instance. This is the implied
+ default.
@@ -164,19 +224,19 @@
dot command (see
above), selects which dependencies are
shown in the dependency graph. If
- is passed
+ is passed,
only dependencies of type
After= or
Before= are
shown. If
- is passed only dependencies of type
+ is passed, only dependencies of type
Requires=,
RequiresOverridable=,
Requisite=,
RequisiteOverridable=,
Wants= and
Conflicts= are
- shown. If neither is passed, shows
+ shown. If neither is passed, this shows
dependencies of all these
types.
@@ -188,16 +248,16 @@
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.
@@ -211,8 +271,23 @@
latest unit in the same level. The unit of
timespan is seconds
unless specified with a different unit,
- i.e. "50ms".
+ e.g. "50ms".
+
+
+
+
+
+ Do not invoke man to verify the existence
+ of man pages listen in Documentation=.
+
+
+
+
+
+
+
+
@@ -220,27 +295,96 @@
Exit status
- On success 0 is returned, a non-zero failure
+ On success, 0 is returned, a non-zero failure
code otherwise.
- Examples
+ Examples for dot
- This plots all dependencies of any unit whose
- name starts with "avahi-daemon.":
+
+ Plots all dependencies of any unit whose
+ name starts with avahi-daemon
- $ systemd-analyze dot 'avahi-daemon.*' | dot -Tsvg > avahi.svg
-$ eog avahi.svg
+ $ systemd-analyze dot 'avahi-daemon.*' | dot -Tsvg > avahi.svg
+ $ eog avahi.svg
+
- This plots the dependencies between all known target units:
+
+ Plots the dependencies between all known target units
- systemd-analyze dot --to-pattern='*.target' --from-patter='*.target' | dot -Tsvg > targets.svg
+ systemd-analyze dot --to-pattern='*.target' --from-pattern='*.target' | dot -Tsvg > targets.svg
$ eog targets.svg
+
+
-
+
+ Examples for verify
+
+ The following errors are currently detected:
+
+ unknown sections and
+ directives,
+
+ missing dependencies which are
+ required to start the given unit,
+
+
+ man pages listed in
+ Documentation= which are
+ not found in the system,
+
+ commands listed in
+ ExecStart= and similar
+ which are not found in the system or not
+ executable.
+
+
+
+ Misspelt directives
+
+ $ cat ./user.slice
+[Unit]
+WhatIsThis=11
+Documentation=man:nosuchfile(1)
+Requires=different.service
+
+[Service]
+Desription=x
+
+$ systemd-verify ./user.slice
+[./user.slice:9] Unknown lvalue 'WhatIsThis' in section 'Unit'
+[./user.slice:13] Unknown section 'Service'. Ignoring.
+Error: org.freedesktop.systemd1.LoadFailed:
+ Unit different.service failed to load:
+ No such file or directory.
+Failed to create user.slice/start: Invalid argument
+user.slice: man nosuchfile(1) command failed with code 16
+
+
+
+
+ Missing service units
+
+ $ tail ./a.socket ./b.socket
+==> ./a.socket <==
+[Socket]
+ListenStream=100
+
+==> ./b.socket <==
+[Socket]
+ListenStream=100
+Accept=yes
+
+$ systemd-verify ./a.socket ./b.socket
+Service a.service not loaded, a.socket cannot be started.
+Service b@0.service not loaded, b.socket cannot be started.
+
+
+
+
See Also