X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd-analyze.xml;h=ae7a3377c65be90c49e60f00bb07d7061f2d7af7;hb=f6c9f322e83a45f8f4da0194dd987d4565155bb0;hp=c8d0b4743b743ba8d0fdefb0795039b2b07b5b50;hpb=e55933db18d1037876e7a0962bcf6ef6c0bbbd68;p=elogind.git diff --git a/man/systemd-analyze.xml b/man/systemd-analyze.xml index c8d0b4743..ae7a3377c 100644 --- a/man/systemd-analyze.xml +++ b/man/systemd-analyze.xml @@ -34,6 +34,12 @@ Poettering lennart@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 @@ -88,25 +110,38 @@ 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 spent on initialization. - systemd-analyze dot - Generate textual dependency graph description in dot - format for further processing with the GraphViz + 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 + 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 patterns may be given at the end. The - relationship is printed if any of these matches either - lefthand or righthand node. + 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. @@ -180,6 +215,19 @@ 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". + @@ -191,6 +239,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