From 359deb60c25147e91a69c227ace686654ea7f484 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Wed, 27 Jun 2012 01:53:07 +0200 Subject: [PATCH] man: write man page for systemd-analyze --- Makefile.am | 3 +- man/systemd-analyze.xml | 138 ++++++++++++++++++++++++++++++++++++++++ 2 files changed, 140 insertions(+), 1 deletion(-) create mode 100644 man/systemd-analyze.xml diff --git a/Makefile.am b/Makefile.am index 04ae77519..84e372f93 100644 --- a/Makefile.am +++ b/Makefile.am @@ -495,7 +495,8 @@ MANPAGES = \ man/systemd-suspend.service.8 \ man/systemd-halt.service.8 \ man/systemd-fsck@.service.8 \ - man/systemd-ask-password-console.service.8 + man/systemd-ask-password-console.service.8 \ + man/systemd-analyze.1 MANPAGES_ALIAS = \ man/reboot.8 \ diff --git a/man/systemd-analyze.xml b/man/systemd-analyze.xml new file mode 100644 index 000000000..960ae7d33 --- /dev/null +++ b/man/systemd-analyze.xml @@ -0,0 +1,138 @@ + + + + + + + + + systemd-analyze + systemd + + + + Developer + Lennart + Poettering + lennart@poettering.net + + + + + + systemd-analyze + 1 + + + + systemd-analyze + Analyze system boot-up performance + + + + + systemd-analyze OPTIONS time + + + systemd-analyze OPTIONS blame + + + systemd-analyze OPTIONS plot > file.svg + + + + + Description + + systemd-analyze may be used + to determine system boot-up performance of the current + boot. + + 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 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. + + systemd-analyze blame 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. + + systemd-analyze plot prints + an SVG graphic detailing which system services have + been started at what time, highlighting the time they + spent on initialization. + + If no command is passed systemd-analyze + time is implied. + + + + + Options + + The following options are understood: + + + + + + + Prints a short help + text and exits. + + + + + + Shows performance data + of user sessions instead of the system + manager. + + + + + + + Exit status + + On success 0 is returned, a non-zero failure + code otherwise. + + + + See Also + + systemd1, + systemctl1 + + + + -- 2.30.2