2012-06-27 03:53:07 +04:00
<?xml version='1.0'?> <!-- * - nxml - * -->
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<!--
This file is part of systemd.
Copyright 2012 Lennart Poettering
systemd is free software; you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or
(at your option) any later version.
systemd is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public License
along with systemd; If not, see <http: / / w w w . g n u . o r g / l i c e n s e s /> .
-->
2014-02-12 09:55:38 +04:00
<refentry id= "systemd-analyze"
xmlns:xi="http://www.w3.org/2001/XInclude">
2012-06-27 03:53:07 +04:00
<refentryinfo >
<title > systemd-analyze</title>
<productname > systemd</productname>
<authorgroup >
<author >
<contrib > Developer</contrib>
<firstname > Lennart</firstname>
<surname > Poettering</surname>
<email > lennart@poettering.net</email>
</author>
2013-04-23 13:11:10 +04:00
<author >
<contrib > Developer</contrib>
<firstname > Harald</firstname>
<surname > Hoyer</surname>
<email > harald@redhat.com</email>
</author>
2012-06-27 03:53:07 +04:00
</authorgroup>
</refentryinfo>
<refmeta >
<refentrytitle > systemd-analyze</refentrytitle>
<manvolnum > 1</manvolnum>
</refmeta>
<refnamediv >
<refname > systemd-analyze</refname>
<refpurpose > Analyze system boot-up performance</refpurpose>
</refnamediv>
<refsynopsisdiv >
<cmdsynopsis >
2013-06-14 16:53:15 +04:00
<command > systemd-analyze</command>
<arg choice= "opt" rep= "repeat" > OPTIONS</arg>
<arg > time</arg>
2012-06-27 03:53:07 +04:00
</cmdsynopsis>
<cmdsynopsis >
2013-06-14 16:53:15 +04:00
<command > systemd-analyze</command>
<arg choice= "opt" rep= "repeat" > OPTIONS</arg>
<arg choice= "plain" > blame</arg>
2012-06-27 03:53:07 +04:00
</cmdsynopsis>
2013-04-23 13:11:10 +04:00
<cmdsynopsis >
2013-06-14 16:53:15 +04:00
<command > systemd-analyze</command>
<arg choice= "opt" rep= "repeat" > OPTIONS</arg>
<arg choice= "plain" > critical-chain</arg>
<arg choice= "opt" rep= "repeat" > <replaceable > UNIT</replaceable> </arg>
2013-04-23 13:11:10 +04:00
</cmdsynopsis>
2012-06-27 03:53:07 +04:00
<cmdsynopsis >
2013-06-14 16:53:15 +04:00
<command > systemd-analyze</command>
<arg choice= "opt" rep= "repeat" > OPTIONS</arg>
<arg choice= "plain" > plot</arg>
<arg choice= "opt" > > file.svg</arg>
2012-06-27 03:53:07 +04:00
</cmdsynopsis>
2013-02-14 02:17:28 +04:00
<cmdsynopsis >
2013-06-14 16:53:15 +04:00
<command > systemd-analyze</command>
<arg choice= "opt" rep= "repeat" > OPTIONS</arg>
<arg choice= "plain" > dot</arg>
<arg choice= "opt" rep= "repeat" > <replaceable > PATTERN</replaceable> </arg>
2013-07-26 18:59:55 +04:00
<arg choice= "opt" > > file.dot</arg>
2013-02-14 02:17:28 +04:00
</cmdsynopsis>
2013-07-26 18:34:52 +04:00
<cmdsynopsis >
<command > systemd-analyze</command>
<arg choice= "opt" rep= "repeat" > OPTIONS</arg>
<arg choice= "plain" > dump</arg>
</cmdsynopsis>
2013-07-26 18:59:55 +04:00
<cmdsynopsis >
<command > systemd-analyze</command>
<arg choice= "opt" rep= "repeat" > OPTIONS</arg>
<arg choice= "plain" > set-log-level</arg>
<arg choice= "opt" > <replaceable > LEVEL</replaceable> </arg>
</cmdsynopsis>
2012-06-27 03:53:07 +04:00
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
<para > <command > systemd-analyze</command> may be used
2013-07-26 18:59:55 +04:00
to determine system boot-up performance statistics and
retrieve other state and tracing information from the
system and service manager.</para>
2012-06-27 03:53:07 +04:00
<para > <command > systemd-analyze time</command>
prints the time spent in the kernel before
userspace has been reached, the time spent in the
initial RAM disk (initrd) before normal system
2013-06-27 23:51:44 +04:00
userspace has been reached, and the time normal system
2012-06-27 03:53:07 +04:00
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
not necessarily until they fully finished
initialization or the disk is idle.</para>
<para > <command > systemd-analyze blame</command> prints
a list of all running units, ordered by the time they
took to initialize. This information may be used to
optimize boot-up times. Note that the output might be
misleading as the initialization of one service might
be slow simply because it waits for the initialization
of another service to complete.</para>
2013-06-14 16:53:15 +04:00
<para > <command > systemd-analyze critical-chain [<replaceable > UNIT...</replaceable> ]</command>
2013-06-27 23:51:44 +04:00
prints a tree of the time-critical chain of units
2013-06-14 16:53:15 +04:00
(for each of the specified <replaceable > UNIT</replaceable> s
or for the default target otherwise).
2013-04-23 13:11:10 +04:00
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.</para>
2012-06-27 03:53:07 +04:00
<para > <command > systemd-analyze plot</command> prints
an SVG graphic detailing which system services have
been started at what time, highlighting the time they
spent on initialization.</para>
2013-07-26 18:34:52 +04:00
<para > <command > systemd-analyze dot</command> generates
2013-04-08 21:42:48 +04:00
textual dependency graph description in dot format for
further processing with the GraphViz
2013-02-14 02:17:28 +04:00
<citerefentry > <refentrytitle > dot</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
tool. Use a command line like <command > systemd-analyze
2013-04-08 21:42:48 +04:00
dot | dot -Tsvg > systemd.svg</command> to generate a
graphical dependency tree. Unless
2013-02-14 02:17:28 +04:00
<option > --order</option> or <option > --require</option>
2013-06-27 23:51:44 +04:00
is passed, the generated graph will show both ordering
2013-04-08 21:42:48 +04:00
and requirement dependencies. Optional pattern
globbing style specifications
(e.g. <filename > *.target</filename> ) 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.</para>
2013-04-06 17:40:56 +04:00
2013-07-26 18:34:52 +04:00
<para > <command > systemd-analyze dump</command> 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.</para>
2013-07-26 18:59:55 +04:00
<para > <command > systemd-analyze set-log-level
<replaceable > LEVEL</replaceable> </command> changes the
current log level of the <command > systemd</command>
daemon to <replaceable > LEVEL</replaceable> (accepts
the same values as <option > --log-level=</option>
described in
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ).</para>
2013-06-27 23:51:44 +04:00
<para > If no command is passed, <command > systemd-analyze
2012-06-27 03:53:07 +04:00
time</command> is implied.</para>
</refsect1>
<refsect1 >
<title > Options</title>
<para > The following options are understood:</para>
<variablelist >
<varlistentry >
2012-06-27 05:58:10 +04:00
<term > <option > -h</option> </term>
2012-06-27 03:53:07 +04:00
<term > <option > --help</option> </term>
<listitem > <para > Prints a short help
text and exits.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > --user</option> </term>
<listitem > <para > Shows performance data
of user sessions instead of the system
manager.</para> </listitem>
</varlistentry>
2013-02-14 02:17:28 +04:00
2013-11-06 20:30:39 +04:00
<varlistentry >
<term > <option > --system</option> </term>
<listitem > <para > Shows performance data
of the system manager. This is the
implied default.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > -H</option> </term>
<term > <option > --host=</option> </term>
2013-11-07 04:17:48 +04:00
<listitem > <para > Execute the operation
2013-11-06 20:30:39 +04:00
remotely. Specify a hostname, or
username and hostname separated by
<literal > @</literal> , to connect
to. This will use SSH to talk to the
remote machine manager
instance.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > -M</option> </term>
<term > <option > --machine=</option> </term>
2013-11-07 04:17:48 +04:00
<listitem > <para > Execute the operation on a
2013-11-06 20:30:39 +04:00
local container. Specify a container
name to connect to.</para> </listitem>
</varlistentry>
2013-02-14 02:17:28 +04:00
<varlistentry >
<term > <option > --order</option> </term>
<term > <option > --require</option> </term>
<listitem > <para > When used in
conjunction with the
<command > dot</command> command (see
above), selects which dependencies are
shown in the dependency graph. If
2013-09-12 23:12:49 +04:00
<option > --order</option> is passed,
2013-02-14 02:17:28 +04:00
only dependencies of type
<varname > After=</varname> or
<varname > Before=</varname> are
shown. If <option > --require</option>
2013-09-12 23:12:49 +04:00
is passed, only dependencies of type
2013-02-14 02:17:28 +04:00
<varname > Requires=</varname> ,
<varname > RequiresOverridable=</varname> ,
<varname > Requisite=</varname> ,
<varname > RequisiteOverridable=</varname> ,
<varname > Wants=</varname> and
<varname > Conflicts=</varname> are
2013-06-27 23:51:44 +04:00
shown. If neither is passed, this shows
2013-02-14 02:17:28 +04:00
dependencies of all these
types.</para> </listitem>
</varlistentry>
2013-04-06 17:40:56 +04:00
<varlistentry >
<term > <option > --from-pattern=</option> </term>
<term > <option > --to-pattern=</option> </term>
<listitem > <para > When used in
conjunction with the
<command > dot</command> command (see
2013-06-27 23:51:44 +04:00
above), this selects which relationships
2013-04-06 17:40:56 +04:00
are shown in the dependency graph.
They both require
<citerefentry > <refentrytitle > glob</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry>
patterns as arguments, which are
2013-06-27 23:51:44 +04:00
matched against left-hand and
right-hand, respectively, nodes of a
2013-04-06 17:40:56 +04:00
relationship. Each of these can be
2013-06-27 23:51:44 +04:00
used more than once, which means a
unit name must match one of the given
2013-04-06 17:40:56 +04:00
values.</para> </listitem>
</varlistentry>
2013-04-23 13:11:10 +04:00
<varlistentry >
<term > <option > --fuzz=</option> <replaceable > timespan</replaceable> </term>
<listitem > <para > When used in conjunction
with the <command > critical-chain</command>
command (see above), also show units, which
finished <replaceable > timespan</replaceable> earlier, than the
latest unit in the same level. The unit of
<replaceable > timespan</replaceable> is seconds
unless specified with a different unit,
2013-06-27 23:51:44 +04:00
e.g. "50ms".</para> </listitem>
2013-04-23 13:11:10 +04:00
</varlistentry>
2013-07-26 18:34:52 +04:00
<varlistentry >
<term > <option > --no-pager</option> </term>
<listitem >
<para > Do not pipe output into a pager.</para>
</listitem>
</varlistentry>
2012-06-27 03:53:07 +04:00
</variablelist>
</refsect1>
<refsect1 >
<title > Exit status</title>
2013-12-26 05:47:44 +04:00
<para > On success, 0 is returned, a non-zero failure
2012-06-27 03:53:07 +04:00
code otherwise.</para>
</refsect1>
2013-04-08 21:42:48 +04:00
<refsect1 >
<title > Examples</title>
<para > This plots all dependencies of any unit whose
2013-06-26 16:03:53 +04:00
name starts with <literal > avahi-daemon.</literal> :</para>
2013-04-08 21:42:48 +04:00
<programlisting > $ systemd-analyze dot 'avahi-daemon.*' | dot -Tsvg > avahi.svg
$ eog avahi.svg</programlisting>
<para > This plots the dependencies between all known target units:</para>
2013-08-22 07:02:46 +04:00
<programlisting > systemd-analyze dot --to-pattern='*.target' --from-pattern='*.target' | dot -Tsvg > targets.svg
2013-04-08 21:42:48 +04:00
$ eog targets.svg</programlisting>
</refsect1>
2014-02-12 09:55:38 +04:00
<xi:include href= "less-variables.xml" />
2013-07-26 18:34:52 +04:00
2012-06-27 03:53:07 +04:00
<refsect1 >
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
</para>
</refsect1>
</refentry>