summaryrefslogtreecommitdiff
path: root/man/systemctl.xml
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #27638 from YHNdnzj/upheldby-unit-fileMike Yuan2023-05-161-5/+4
|\ | | | | unit-file: support UpheldBy= in [Install] settings (adding Upholds= deps from .upholds/)
| * unit-file: support UpheldBy= in [Install] settings (adding Upholds= depsMike Yuan2023-05-151-5/+4
| | | | | | | | | | | | from .upholds/) Closes #26896
* | man: indicate that the JOB parameter to "systemctl cancel" is optionalLennart Poettering2023-05-161-1/+1
|/ | | | | | As per: https://social.treehouse.systems/@grawity/110376583742207755
* core/systemctl: when switching root default to /sysroot/Lennart Poettering2023-04-281-9/+10
| | | | | | | | | We hardcode the path the initrd uses to prepare the final mount point at so many places, let's also imply it in "systemctl switch-root" if not specified. This adds the fallback both to systemctl and to PID 1 (this is because both to — different – checks on the path).
* tree-wide: code spelling fixesFrantisek Sumsal2023-04-201-1/+1
| | | | As reported by Fossies.
* service: allow freeing the fdstore via cleaningLennart Poettering2023-04-131-10/+18
| | | | | | Now that we have a potentially pinned fdstore let's add a concept for cleaning it explicitly on user requested. Let's expose this via "systemctl clean", i.e. the same way as user directories are cleaned.
* man: document image policy syntax and semantics, and the hooks in the ↵Lennart Poettering2023-04-051-0/+2
| | | | various components
* systemctl: add option --when for scheduled shutdownMike Yuan2023-03-141-18/+23
| | | | | | | Pass an empty string or "cancel" will cancel the action. Pass "show" will show the scheduled actions. Replaces #17258
* systemctl: warn if units disabled in user scope are still enabled globallyMike Yuan2023-02-221-1/+10
| | | | Fixes #18271
* tree-wide: fix typoYu Watanabe2023-02-221-1/+1
|
* Merge pull request #26491 from dtardon/list-pathsYu Watanabe2023-02-221-0/+20
|\ | | | | Add systemctl list-paths
| * man: document systemctl list-pathsDavid Tardon2023-02-211-0/+20
| |
* | man: document new --kill-value= switch to systemctlLennart Poettering2023-02-171-34/+41
|/
* systemctl: list-dependencies: support --type= and --state=Mike Yuan2023-01-161-5/+9
| | | | Closes #25975
* systemctl: suppress warning about missing /proc/ when --no-warnYu Watanabe2023-01-121-4/+12
| | | | | | | | | Follow-up for 0f958c8d4fc13ed1c1af928b2a7d91d31c7576eb. systemctl is called many times by dnf or so, and missing /proc/ is not a user's fault, but package manager's issue. With this commit, we can suppress the warning by updating rpm macros if necessary.
* systemctl: new option --drop-in for specifying drop-in filenameMike Yuan2022-12-201-0/+12
| | | | | | | | | Previously 'systemctl edit' would only operate on 'override.conf', but users may need more than that. Thus the new option '--drop-in' is added to allow users to specify the drop-in file name. Closes #25767
* systemctl: is-enabled: document the return code changeMike Yuan2022-12-141-0/+5
| | | | | | Follow-up for #25689 We've added a new output ("not-found") in #25689.
* Merge pull request #25437 from ↵Zbigniew Jędrzejewski-Szmek2022-12-051-2/+16
|\ | | | | | | | | YHNdnzj/systemctl-disable-warn-statically-enabled-services systemctl: warn if trying to disable a unit with no install info
| * systemctl: allow suppress the warning of no install info using --no-warnMike Yuan2022-12-031-2/+16
| | | | | | | | | | | | In cases like packaging scripts, it might be desired to use enable/disable on units without install info. So, adding an option '--no-warn' to suppress the warning.
* | tree-wide: BLS and DPS are now on uapi-group websiteZbigniew Jędrzejewski-Szmek2022-11-211-1/+1
|/
* man: use the correct 'Markers' property name for marking unitsFrantisek Sumsal2022-11-021-1/+1
| | | | Follow-up to c9615f7352 and 70666e28a1.
* man: fix count mismatchZbigniew Jędrzejewski-Szmek2022-10-241-1/+1
| | | | We said "search path" and "search paths" in the same sentence…
* systemctl: add support for --image optionRichard Phibel2022-09-271-0/+13
| | | | | All tools that support --root= should also learn --image= so that they can operate on disk images directly.
* Merge pull request #24709 from keszybz/partition-table-constantsLennart Poettering2022-09-211-10/+11
|\ | | | | Expose various GPT UUIDs as public contants and link them up in docs
| * man: "the initial RAM disk" → "the initrd"Zbigniew Jędrzejewski-Szmek2022-09-201-9/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In many places we spelled out the phrase behind "initrd" in full, but this isn't terribly useful. In fact, no "RAM disk" is used, so emphasizing this is just confusing to the reader. Let's just say "initrd" everywhere, people understand what this refers to, and that it's in fact an initramfs image. Also, s/i.e./e.g./ where appropriate. Also, don't say "in RAM", when in fact it's virtual memory, whose pages may or may not be loaded in page frames in RAM, and we have no control over this. Also, add <filename></filename> and other minor cleanups.
| * man: add missing subject in sentenceZbigniew Jędrzejewski-Szmek2022-09-171-1/+1
| |
* | various: use "-" instead of "n/a" in tablesZbigniew Jędrzejewski-Szmek2022-09-171-1/+1
|/ | | | | | | | In the context of a table, both would be generally understood to have the same meaning. "n/a" is a strange beast. It was useful when tables were produced on the typewriter with "---------" used to separate rows. It is visually more pleasing to use "-", and there is no risk of it being mistaken for a row separator.
* tree-wide: change --kill-who to --kill-whomZbigniew Jędrzejewski-Szmek2022-08-261-2/+2
| | | | | | | | | | | getopt allows non-ambiguous abbreviations, so backwards-compat is maintained, and people can use --kill-who (or even shorter abbreviations). English is flexible, so in common speach people would use both forms, even if "whom" is technically more correct. The advantage of using the longer form in the code is that we effectively allow both forms, so we stop punishing people who DTGCT¹, but still allow people to use the spoken form if they prefer. 1. Do the gramatically correct thing
* man: fix docbookLennart Poettering2022-08-031-1/+1
|
* systemctl: clarify that "status" is about the most recent invocation of a ↵Lennart Poettering2022-08-031-19/+18
| | | | | | | | service And point people to "journalctl --unit=" for information of prior runs. Inspired by: #24159
* man: document systemctl list-automountsDavid Tardon2022-07-251-0/+19
|
* Merge pull request #15205 from jlebon/pr/preset-all-firstbootZbigniew Jędrzejewski-Szmek2022-07-061-1/+1
|\ | | | | manager: optionally, do a full preset on first boot
| * systemctl: stop saying "vendor preset"Zbigniew Jędrzejewski-Szmek2022-05-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We have vendor presets, and local admin presets, and runtime presets (under /usr/lib, /usr/local/lib and /etc, /run, respectively). When we display preset state, it can be configured in any of those places, so we shouldn't say anything about the origin. (Another nice advantage is that it improves alignment: [root@f36 ~]# systemctl list-unit-files multipathd.service UNIT FILE STATE VENDOR PRESET multipathd.service enabled enabled ^ this looks we have a "PRESET" column that is empty.)
* | man: "enabled commands are started at boot" is rubbishLennart Poettering2022-07-061-20/+22
| | | | | | | | | | | | | | it's enabled units, and they might be started by various forms of activation, not just "at boot". Fix that.
* | man/systemctl: improve grammar in description of --check-inhibitorsZbigniew Jędrzejewski-Szmek2022-06-011-16/+14
| |
* | systemctl: make show/status honour --state and --typeZbigniew Jędrzejewski-Szmek2022-05-261-26/+22
|/ | | | | | | This makes the interface more flexible, by allowing the same filtering for show and status as is done for list-units. Fixes #23207.
* man: cross-advertize bootctl and systemctl boot loader supportZbigniew Jędrzejewski-Szmek2022-04-281-6/+12
|
* docs: s/straight-forward/straightforward/Lennart Poettering2022-03-151-1/+1
| | | | Inspired by https://github.com/systemd/systemd/pull/20156#discussion_r810878846
* systemctl,man: update docs for `--timestamp=`Frantisek Sumsal2022-02-211-0/+7
|
* docs: Clarify systemctl show manualPaulo Neves2021-11-091-2/+2
| | | | | | | | | | The manual incorrectly asserted that the properties in systemctl show matched the the options in systemd-system.conf, which is not always true. Add clarification on the equivalence of the properties in systemctl show and systemd-system.conf Fixed #21230
* man: clarify the situation of unit templates regarding "systemctl ↵Lennart Poettering2021-10-281-9/+19
| | | | | | list-units" + "systemctl list-unit-files" Fixes: #21075
* man/systemctl: rework descriptions of bind and mount-imageZbigniew Jędrzejewski-Szmek2021-07-281-44/+69
| | | | | | | | | The text used "unit's view" to mean mount namespace. But we talk about mount namespaces in the later part of the paragraph anyway, so trying to use an "approachable term" only makes the whole thing harder to understand. Let's use the precise term. Some paragraph-breaking and re-indentation is done too.
* man: describe various logging configuration variablesZbigniew Jędrzejewski-Szmek2021-03-011-0/+5
| | | | | | | Fixes #17484. This patch affects systemctl(1), as well as all man pages that include all of common-variables.xml, i.e. most of our command line tools.
* man: rename less-variables→common-variablesZbigniew Jędrzejewski-Szmek2021-03-011-6/+6
| | | | Some are not about less, e.g. $SYSTEMD_URLIFY.
* Merge pull request #18596 from keszybz/systemctl-quiet-legendLennart Poettering2021-02-171-1/+1
|\ | | | | systemctl: hide legends with --quiet, allow overriding
| * systemctl: hide legends with --quiet, allow overridingZbigniew Jędrzejewski-Szmek2021-02-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | --no-legend is replaced by --legend=no. --quiet now implies --legend=no, but --legend=yes may be used to override that. --quiet controls hints and warnings and such, and --legend controls just the legends. I think it makes sense to allow both to controlled independently, in particular --quiet --legend makes sense when using systemctl in a script to provide some user-visible output. Fixes #18560.
* | Merge pull request #18481 from keszybz/rpm-restart-post-transZbigniew Jędrzejewski-Szmek2021-02-161-0/+12
|\ \ | |/ |/| Restart units after the rpm transaction
| * systemctl: add "reload-or-restart --marked"Zbigniew Jędrzejewski-Szmek2021-02-151-0/+12
| | | | | | | | | | | | This is almost equivalent to 'busctl call-method org.freedesktop.systemd1 /org/freedesktop/systemd1 org.freedesktop.systemd1.Manager EnqueueMarkedJobs', but waits for the jobs to finish.
* | systemctl,loginctl,machinectl: use a shared helper for arg_signalZbigniew Jędrzejewski-Szmek2021-02-141-13/+1
|/ | | | | I seems frivolous to yet another two -util.[ch] files, but the helper should be in shared/ and it doesn't seem to fit anywhere else.
* man: move content from the wiki to systemd.preset(5)Zbigniew Jędrzejewski-Szmek2021-02-021-3/+1
| | | | | | | | | | The wiki was slightly stale, and almost all the information there was already present in the man page. I moved the remaing part (discussion) into the man page and adjusted all links to point to the man page instead. daemon(7) has a some examples of packaging scriptlets… I don't think it fits there very well. Most likely they should be moved to systemd.preset(5) or maybe even removed, but I'm leaving that for later.
View Lorry Controller Status