summaryrefslogtreecommitdiffstats
path: root/man/systemd-analyze.xml (follow)
Commit message (Collapse)AuthorAgeFilesLines
* systemd-analyze: fixed typo in documentationTobias Stoeckmann2020-01-021-1/+1
| | | | | The example shows the output of critical-chain, which means that the title is wrong.
* man: change noindex="true" to index="false"Zbigniew Jędrzejewski-Szmek2019-11-211-3/+3
| | | | We nowadays prefer positive options over negative.
* analyze: deprecate the commands moved to systemctlZbigniew Jędrzejewski-Szmek2019-11-181-50/+0
| | | | | This just removes the commands from --help and the man pages, everything works as before.
* man: document --base-time= for systemd-analyzeLennart Poettering2019-11-131-0/+7
|
* analyze: rename "exit-codes" to "exit-status"Lennart Poettering2019-07-291-14/+14
| | | | | | waitid(2) and the libc function signature calls this "exit status", and uses "exit code" for something different. Let's stick to the same nomenclature hence.
* analyze: add exit-codes verbZbigniew Jędrzejewski-Szmek2019-07-291-0/+30
|
* man: document that "systemd-analyze blame/critical-chain" is not useful to ↵Lennart Poettering2019-07-121-2/+13
| | | | | | track down job latency Fixes: #12272
* analyze: add 'condition' verbZbigniew Jędrzejewski-Szmek2019-06-271-0/+33
| | | | | We didn't have a straightforward way to parse and evaluate those strings. Prompted by #12881.
* analyze: also print unix time in "timestamp"Zbigniew Jędrzejewski-Szmek2019-05-211-7/+10
|
* analyze: add 'timestamp' verbZbigniew Jędrzejewski-Szmek2019-05-171-6/+44
| | | | | | | | | We had 'calendar' and 'timespan', but the third one was missing. Also consistently order the verbs as calendar/timestamp/timespan in help. The output from 'timespan' is highlighted more. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1711065.
* codespell: fix spelling errorsBen Boeckel2019-04-291-1/+1
|
* man: reorder and add examples to systemd-analyze(1)Zbigniew Jędrzejewski-Szmek2019-03-151-258/+431
| | | | | | | The number of verbs supported by systemd-analyze has grown quite a bit, and the man page has become an unreadable wall of text. Let's put each verb in a separate subsection, grouping similar verbs together, and add a lot of examples to guide the user.
* man: use same header for all filesZbigniew Jędrzejewski-Szmek2019-03-141-1/+1
| | | | | | | The "include" files had type "book" for some raeason. I don't think this is meaningful. Let's just use the same everywhere. $ perl -i -0pe 's^..DOCTYPE (book|refentry) PUBLIC "-//OASIS//DTD DocBook XML V4.[25]//EN"\s+"http^<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"\n "http^gms' man/*.xml
* man: standarize on one-line license headerZbigniew Jędrzejewski-Szmek2019-03-141-4/+1
| | | | | | No need to waste space, and uniformity is good. $ perl -i -0pe 's|\n+<!--\s*SPDX-License-Identifier: LGPL-2.1..\s*-->|\n<!-- SPDX-License-Identifier: LGPL-2.1+ -->|gms' man/*.xml
* analyze: optionally, show more than one elapse time for calendar expressionsLennart Poettering2019-02-221-5/+15
|
* man: document systemd-analyze securityLennart Poettering2018-11-301-0/+29
|
* analyze: Add "timespan" command to dump time span in usecChris Down2018-10-231-0/+10
| | | | | | | | | | | | | | | | | | | | | | This is useful for a couple of cases, I'm mostly interested in case #1: 1. Verifying "reasonable" values in a trivially scriptable way 2. Debugging unexpected time span parsing directly Test Plan: ``` % build/systemd-analyze timespan 20 Original: 20 μs: 20 Human: 20us % build/systemd-analyze timespan 20ms Original: 20ms μs: 20000 Human: 20ms % build/systemd-analyze timespan 20z Failed to parse time span '20z': Invalid argument ```
* man: drop unused <authorgroup> tags from man sourcesZbigniew Jędrzejewski-Szmek2018-06-141-15/+0
| | | | | | | | | | | | Docbook styles required those to be present, even though the templates that we use did not show those names anywhere. But something changed semi-recently (I would suspect docbook templates, but there was only a minor version bump in recent years, and the changelog does not suggest anything related), and builds now work without those entries. Let's drop this dead weight. Tested with F26-F29, debian unstable. $ perl -i -0pe 's/\s*<authorgroup>.*<.authorgroup>//gms' man/*xml
* tree-wide: remove Lennart's copyright linesLennart Poettering2018-06-141-2/+0
| | | | | | | | | | | These lines are generally out-of-date, incomplete and unnecessary. With SPDX and git repository much more accurate and fine grained information about licensing and authorship is available, hence let's drop the per-file copyright notice. Of course, removing copyright lines of others is problematic, hence this commit only removes my own lines and leaves all others untouched. It might be nicer if sooner or later those could go away too, making git the only and accurate source of authorship information.
* tree-wide: drop 'This file is part of systemd' blurbLennart Poettering2018-06-141-3/+0
| | | | | | | | | | | | | | | | This part of the copyright blurb stems from the GPL use recommendations: https://www.gnu.org/licenses/gpl-howto.en.html The concept appears to originate in times where version control was per file, instead of per tree, and was a way to glue the files together. Ultimately, we nowadays don't live in that world anymore, and this information is entirely useless anyway, as people are very welcome to copy these files into any projects they like, and they shouldn't have to change bits that are part of our copyright header for that. hence, let's just get rid of this old cruft, and shorten our codebase a bit.
* doc: more spelling fixesMichael Biebl2018-06-121-1/+1
|
* Merge pull request #8824 from keszybz/analyze-show-configLennart Poettering2018-05-101-0/+41
|\ | | | | systemd-analyze show-config
| * analyze: allow full paths for cat-configZbigniew Jędrzejewski-Szmek2018-05-071-2/+6
| | | | | | | | | | | | | | | | | | $ systemd-analyze cat-config systemd/logind.conf $ systemd-analyze cat-config /etc/systemd/logind.conf $ systemd-analyze cat-config /usr/lib/systemd/logind.conf are all equvalent, $ systemd-analyze cat-config /var/systemd/logind.conf is an error.
| * analyze: add --root option for cat-configZbigniew Jędrzejewski-Szmek2018-04-271-0/+7
| |
| * analyze: add 'cat-config' verbZbigniew Jędrzejewski-Szmek2018-04-271-0/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is used as 'systemd-analyze show-config systemd/logind.conf', which will dump /etc/systemd/system/user@.service /etc/systemd/system/user@.service.d/*.conf /run/systemd/system/user@.service.d/*.conf /usr/local/lib/systemd/system/user@.service.d/*.conf /usr/lib/systemd/system/user@.service.d/*.conf The idea is to make it easy to dump the configuration using the same locations and order that systemd programs use themselves (including masking, in the right order, etc.). This is the generic variant that works with any configuration scheme that follows the same general rules: $ systemd-analyze cat-config systemd/system.conf $ systemd-analyze cat-config systemd/user.conf $ systemd-analyze cat-config systemd/logind.conf $ systemd-analyze cat-config systemd/sleep.conf $ systemd-analyze cat-config systemd/journald.conf $ systemd-analyze cat-config systemd/journal-remote.conf $ systemd-analyze cat-config systemd/journal-upload.conf $ systemd-analyze cat-config systemd/coredump.conf $ systemd-analyze cat-config systemd/resolved.conf $ systemd-analyze cat-config systemd/timesyncd.conf $ systemd-analyze cat-config udev/udev.conf
* | man: updated systemd-analyze blame description for service-units with ↵Mikhail Kasimov2018-04-271-1/+5
|/ | | | | Type=simple (#8834) Fixes #5121.
* tree-wide: drop license boilerplateZbigniew Jędrzejewski-Szmek2018-04-061-13/+0
| | | | | | | | | | Files which are installed as-is (any .service and other unit files, .conf files, .policy files, etc), are left as is. My assumption is that SPDX identifiers are not yet that well known, so it's better to retain the extended header to avoid any doubt. I also kept any copyright lines. We can probably remove them, but it'd nice to obtain explicit acks from all involved authors before doing that.
* analyze: add unit-paths verbZbigniew Jędrzejewski-Szmek2018-02-091-0/+17
|
* analyze: add --global optionZbigniew Jędrzejewski-Szmek2018-02-081-3/+10
| | | | This is somewhat useful for 'verify', and will be used later with 'unit-paths'.
* man: fix awkward sentence in systemd-analyze(8)Zbigniew Jędrzejewski-Szmek2018-02-021-3/+2
| | | | Closes #8070.
* analyze: merge {get,set}-log-{level,target} to log-{level,target} (#8020)Yu Watanabe2018-01-271-31/+16
| | | | Also, service-watchdogs now shows current watchdog state when no optional argument is provided.
* systemd-analyze: add service-watchdogs verbJan Klötzke2018-01-221-2/+16
| | | | | | New debug verb that enables or disables the service runtime watchdogs and emergency actions during runtime. This is the systemd-analyze version of the systemd.service_watchdogs command line option.
* analyze: add new "calendar" commandLennart Poettering2017-11-201-0/+12
| | | | | | | This little new command can parse, validate, normalize calendar events, and calculate when they will elapse next. This should be useful for anyone writing calendar events and who'd like to validate the expression before running them as timer units.
* Add SPDX license identifiers to man pagesZbigniew Jędrzejewski-Szmek2017-11-191-0/+2
|
* analyze-verify: add --generators switch to enable generators againZbigniew Jędrzejewski-Szmek2017-09-191-1/+11
|
* analyze: add get-log-level, get-log-target verbsLucas Werkmeister2017-09-071-0/+16
| | | | | | | They’re counterparts to the existing set-log-level and set-log-target verbs, simply printing the current value to stdout. This makes it slightly easier to temporarily change the log level and/or target and then restore the old value(s).
* man: fix systemd-analyze plot commands (#6761)John Lin2017-09-071-2/+2
|
* man: fix typos (#5109)Jakub Wilk2017-01-191-1/+1
|
* man: two trivial formatting fixesZbigniew Jędrzejewski-Szmek2016-12-111-1/+1
|
* man: use unicode ellipsis in more placesZbigniew Jędrzejewski-Szmek2016-12-111-3/+3
| | | | | | | | | | | | | | As requested in https://github.com/systemd/systemd/pull/4864#pullrequestreview-12372557. docbook will substitute triple dots for the ellipsis in man output, so this has no effect on the troff output, only on HTML, making it infinitesimally nicer. In some places we show output from programs, which use dots, and those places should not be changed. In some tables, the alignment would change if dots were changed to the ellipsis which is only one character. Since docbook replaces the ellipsis automatically, we should leave those be. This patch changes all other places.
* analyze: add syscall-filter verbZbigniew Jędrzejewski-Szmek2016-11-031-0/+11
| | | | | This should make it easier for users to understand what each filter means as the list of syscalls is updated in subsequent systemd versions.
* analyze-verify: honour $SYSTEMD_UNIT_PATH, allow system paths to be ignoredZbigniew Jędrzejewski-Szmek2016-10-011-8/+9
| | | | | | | | | SYSTEMD_UNIT_PATH=foobar: systemd-analyze verify barbar/unit.service will load units from barbar/, foobar/, /etc/systemd/system/, etc. SYSTEMD_UNIT_PATH= systemd-analyze verify barbar/unit.service will load units only from barbar/, which is useful e.g. when testing systemd's own units on a system with an older version of systemd installed.
* core: remove support for RequiresOverridable= and RequisiteOverridable=Lennart Poettering2015-11-121-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | As discussed at systemd.conf 2015 and on also raised on the ML: http://lists.freedesktop.org/archives/systemd-devel/2015-November/034880.html This removes the two XyzOverridable= unit dependencies, that were basically never used, and do not enhance user experience in any way. Most folks looking for the functionality this provides probably opt for the "ignore-dependencies" job mode, and that's probably a good idea. Hence, let's simplify systemd's dependency engine and remove these two dependency types (and their inverses). The unit file parser and the dbus property parser will now redirect the settings/properties to result in an equivalent non-overridable dependency. In the case of the unit file parser we generate a warning, to inform the user. The dbus properties for this unit type stay available on the unit objects, but they are now hidden from usual introspection and will always return the empty list when queried. This should provide enough compatibility for the few unit files that actually ever made use of this.
* doc: correct punctuation and improve typography in documentationJan Engelhardt2015-11-061-1/+1
|
* man: add "systemd-analyze set-log-target" to synopsis tooLennart Poettering2015-10-061-0/+6
| | | | It's already documented in prose, now add it to the synopsis too.
* man: LEVEL in systemd-analyze set-log level is not optionalLukas Nykryn2015-10-051-1/+1
| | | | rhbz#1268336
* analyze: add new set-log-target subcommandLennart Poettering2015-09-301-0/+7
| | | | | We already have the property writable, hence let's add a command to set it.
* man: revert dynamic paths for split-usr setupsTom Gundersen2015-06-181-4/+1
| | | | | | | | | | | | | | | | | | | | | | | This did not really work out as we had hoped. Trying to do this upstream introduced several problems that probably makes it better suited as a downstream patch after all. At any rate, it is not releaseable in the current state, so we at least need to revert this before the release. * by adjusting the path to binaries, but not do the same thing to the search path we end up with inconsistent man-pages. Adjusting the search path too would be quite messy, and it is not at all obvious that this is worth the effort, but at any rate it would have to be done before we could ship this. * this means that distributed man-pages does not make sense as they depend on config options, and for better or worse we are still distributing man pages, so that is something that definitely needs sorting out before we could ship with this patch. * we have long held that split-usr is only minimally supported in order to boot, and something we hope will eventually go away. So before we start adding even more magic/effort in order to make this work nicely, we should probably question if it makes sense at all.
* man: generate configured paths in manpagesFilipe Brandenburger2015-05-281-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In particular, use /lib/systemd instead of /usr/lib/systemd in distributions like Debian which still have not adopted a /usr merge setup. Use XML entities from man/custom-entities.ent to replace configured paths while doing XSLT processing of the original XML files. There was precedent of some files (such as systemd.generator.xml) which were already using this approach. This addresses most of the (manual) fixes from this patch: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/patches/Fix-paths-in-man-pages.patch?h=experimental-220 The idea of using generic XML entities was presented here: http://lists.freedesktop.org/archives/systemd-devel/2015-May/032240.html This patch solves almost all the issues, with the exception of: - Path to /bin/mount and /bin/umount. - Generic statements about preference of /lib over /etc. These will be handled separately by follow up patches. Tested: - With default configure settings, ran "make install" to two separate directories and compared the output to confirm they matched exactly. - Used a set of configure flags including $CONFFLAGS from Debian: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/rules Installed the tree and confirmed the paths use /lib/systemd instead of /usr/lib/systemd and that no other unexpected differences exist. - Confirmed that `make distcheck` still passes.
* man: fix a bunch of linksZbigniew Jędrzejewski-Szmek2015-03-141-2/+2
| | | | All hail linkchecker!
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-12 06:15:07 +0100