summaryrefslogtreecommitdiff
path: root/man/systemd.service.xml
Commit message (Collapse)AuthorAgeFilesLines
* man/systemd.service: add example for char prefixesZbigniew Jędrzejewski-Szmek2023-04-041-1/+12
| | | | | The prefixes can be specified for any part of the command. The docs imply this, but it's not entirely obvious. Let's add an example.
* man: move description of command line substitution out of ExecStart=Zbigniew Jędrzejewski-Szmek2023-04-041-76/+69
| | | | | | | | The description was split — part was under ExecStart= and part in "Command lines". Now the whole generic part is moved to the separate section, and under ExecStart= only the stuff that is specific to that option is described. This just moves the text and removes some repetitions.
* analyze: add new fdstore verbLennart Poettering2023-03-291-1/+12
|
* core: add RestartSteps= and RestartSecMax= for exponentially increasingMike Yuan2023-03-271-0/+19
| | | | | | | | | | interval between restarts RestartSteps= accepts a positive integer as the number of steps to take to increase the interval between auto-restarts from RestartSec= to RestartSecMax=, or 0 to disable it. Closes #6129
* core: split system/user job timeouts and make them configurableZbigniew Jędrzejewski-Szmek2023-02-011-5/+6
| | | | | | | | | | | | | | | | Config options are -Ddefault-timeout-sec= and -Ddefault-user-timeout-sec=. Existing -Dupdate-helper-user-timeout= is renamed to -Dupdate-helper-user-timeout-sec= for consistency. All three options take an integer value in seconds. The renaming and type-change of the option is a small compat break, but it's just at compile time and result in a clear error message. I also doubt that anyone was actually using the option. This commit separates the user manager timeouts, but keeps them unchanged at 90 s. The timeout for the user manager is set to 4/3*user-timeout, which means that it is still 120 s. Fedora wants to experiment with lower timeouts, but doing this via a patch would be annoying and more work than necessary. Let's make this easy to configure.
* tree-wide: fix typoYu Watanabe2023-01-201-1/+1
|
* man: note that cgroup-based sandboxing is not bypassed by '+'Luca Boccassi2023-01-181-1/+1
| | | | | | | | DeviceAllow= and others are applied to the whole cgroup via bpf, so using '+' on an Exec line will not bypass them. Explain this in the manpage. Fixes https://github.com/systemd/systemd/issues/26035
* man: document Type=notify-reloadLennart Poettering2023-01-101-110/+138
|
* core: add OpenFile settingRichard Phibel2023-01-101-0/+31
|
* core,man: add missing integration of OOMPolicy= in scopesZbigniew Jędrzejewski-Szmek2022-12-131-12/+10
| | | | Fixup for 5fa098357e0ea9f05b00ed5b04a36ef9f64037db.
* man: rework description of OOMPolicy= a bitZbigniew Jędrzejewski-Szmek2022-12-131-9/+10
| | | | | | One had to read to the very end of the long description to notice that the setting is actually primarily intended for oomd. So let's mention oomd right at the beginning.
* tree-wide: replace "plural(s)" by "plurals"Zbigniew Jędrzejewski-Szmek2022-10-171-2/+2
| | | | | | | | (s) is just ugly with a vibe of DOS. In most cases just using the normal plural form is more natural and gramatically correct. There are some log_debug() statements left, and texts in foreign licenses or headers. Those are not touched on purpose.
* man: similar → similarlyZbigniew Jędrzejewski-Szmek2022-08-231-3/+3
| | | | | | | | | Something *is* similar Something *works* similarly Something does something, similarly to how something else does something See https://sites.ulethbridge.ca/roussel/2017/11/29/similar-and-similarly-are-they-similar/ for a clear explanation.
* tree-wide: link to docs.kernel.org for kernel documentationnl67202022-07-041-2/+2
| | | | | | | https://www.kernel.org/ links to https://docs.kernel.org/ for the documentation. See https://git.kernel.org/pub/scm/docs/kernel/website.git/commit/?id=ebc1c372850f249dd143c6d942e66c88ec610520 These URLs are shorter and nicer looking.
* tree-wide: use html links for kernel docsZbigniew Jędrzejewski-Szmek2022-07-021-1/+1
| | | | Instead of using "*.txt" as reference name, use the actual destination title.
* man: direct users to systemd-oomd if they read about OOMPolicyZbigniew Jędrzejewski-Szmek2022-04-281-2/+8
| | | | OOMPolicy remains valid, but let's push users for the userspace solution.
* man: beef up the description of systemd-oomd.serviceZbigniew Jędrzejewski-Szmek2022-04-281-5/+9
| | | | | | | | | | | | The gist of the description is moved from systemd.resource-control to systemd-oomd man page. Cross-references to OOMPolicy, memory.oom.group, oomctl, ManagedOOMSwap and ManagedOOMMemoryPressure are added in all places. The descriptions are also more down-to-earth: instead of talking about "taking action" let's just say "kill". We *might* add configuration for different actions in the future, but we're not there yet, so let's just describe what we do now.
* man: Mention systemd-oomd now follows OOMPolicyNishal Kulkarni2022-03-221-1/+5
|
* Reintroduce ExitTypeHenri Chain2021-11-081-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This introduces `ExitType=main|cgroup` for services. Similar to how `Type` specifies the launch of a service, `ExitType` is concerned with how systemd determines that a service exited. - If set to `main` (the current behavior), the service manager will consider the unit stopped when the main process exits. - The `cgroup` exit type is meant for applications whose forking model is not known ahead of time and which might not have a specific main process. The service will stay running as long as at least one process in the cgroup is running. This is intended for transient or automatically generated services, such as graphical applications inside of a desktop environment. Motivation for this is #16805. The original PR (#18782) was reverted (#20073) after realizing that the exit status of "the last process in the cgroup" can't reliably be known (#19385) This version instead uses the main process exit status if there is one and just listens to the cgroup empty event otherwise. The advantages of a service with `ExitType=cgroup` over scopes are: - Integrated logging / stdout redirection - Avoids the race / synchronisation issue between launch and scope creation - More extensive use of drop-ins and thus distro-level configuration: by moving from scopes to services we can have drop ins that will affect properties that can only be set during service creation, like `OOMPolicy` and security-related properties - It makes systemd-xdg-autostart-generator usable by fixing [1], as obviously only services can be used in the generator, not scopes. [1] https://bugs.kde.org/show_bug.cgi?id=433299
* core: implement RuntimeMaxDeltaSec directiveAlbert Brox2021-09-281-0/+9
|
* man: mention pages with more settings at end of each option listZbigniew Jędrzejewski-Szmek2021-09-271-3/+8
| | | | | | | | | | | For some unit types we have hundreds of options, and the reader may easily miss that more options are described in other pages. We already mentioned this in the introduction and then at the top of the option list, but it can't hurt to repeat the information. Also, add an (almost empty) Options section for the unit types which don't have any custom options. It is nicer to have the same page structure in all cases, so people can jump between pages for different types more easily.
* man: refresh description of sysvinit compat for servicesZbigniew Jędrzejewski-Szmek2021-09-271-9/+5
| | | | | | | | The existing text must have been written before systemd-sysv-generator was created. We don't create the wrappers dynamically since a long time. Also add more links and make the description conditional on "if compat is enabled".
* man: fix assorted issues reported by the manpage-l10n projectZbigniew Jędrzejewski-Szmek2021-07-271-1/+1
| | | | Fixes #20297.
* Revert "Introduce ExitType"Zbigniew Jędrzejewski-Szmek2021-06-301-25/+0
| | | | | | | | | | | This reverts commit cb0e818f7cc2499d81ef143e5acaa00c6e684711. After this was merged, some design and implementation issues were discovered, see the discussion in #18782 and #19385. They certainly can be fixed, but so far nobody has stepped up, and we're nearing a release. Hopefully, this feature can be merged again after a rework. Fixes #19345.
* Introduce ExitTypeHenri Chain2021-03-311-0/+25
|
* man: document differences in clean exit status for Type=oneshotDavid Tardon2021-03-231-9/+14
| | | | See commit 1f0958f640b87175cd547c1e69084cfe54a22e9d .
* man: move quoting description to systemd.syntaxZbigniew Jędrzejewski-Szmek2021-03-011-88/+10
| | | | | We use very similar quoting rules in many places. Let's move this lengthy text out of systemd.service page.
* man: emphasize a bit more that PID files suckLennart Poettering2021-02-191-1/+5
|
* man: various typos and other small issuesZbigniew Jędrzejewski-Szmek2021-01-291-1/+1
| | | | Fixes #18397.
* license: LGPL-2.1+ -> LGPL-2.1-or-laterYu Watanabe2020-11-091-1/+1
|
* man: document that for Type=dbus services dropping bus name has consequencesLennart Poettering2020-10-191-6/+12
| | | | Fixes: #17150
* Merge pull request #17238 from keszybz/man-tmp-noexecLennart Poettering2020-10-071-1/+1
|\ | | | | Say that noexec should not be used for /tmp
| * man: use trailing slash on directories in more placesZbigniew Jędrzejewski-Szmek2020-10-051-1/+1
| |
* | man: fix typosSamanta Navarro2020-10-031-1/+1
|/
* man: do not index various /foobar/ pathsZbigniew Jędrzejewski-Szmek2020-09-301-1/+1
| | | | For #17177.
* systemctl: add service-log-{level,target} verbsZbigniew Jędrzejewski-Szmek2020-09-121-4/+5
| | | | | | | | | | | Heavily inspired by #15622. This adds: systemctl service-log-level systemd-resolved systemctl service-log-level systemd-resolved info systemctl service-log-target systemd-resolved systemctl service-log-target systemd-resolved console We already have systemctl verbs log-level, log-target, and service-watchdogs. Those two new verbs tie nicely into this scheme.
* doc: cross link sd_listen_fd() docs a bitLennart Poettering2020-09-011-13/+17
| | | | | | | | | | | Let's make sure the sd_listen_fd() docs are really found from the .socket file documentation as well as the FileDescriptorStoreMax= documentation. Let's also emphasize that that's where the order in which the fds are passed are documented. Fixes: #16647
* man: fix a fix of a typo in systemd.service exampleJan Chren2020-08-241-2/+2
| | | | The fix from cb263973acf83de22a86f08fe502a9cbd6c01d2b was made the other way around, i.e. `SIGKILL` was changed to `SIGUSR1`, but the sentence is about a "termination signal", i.e. `SIGKILL`, not `SIGUSR1`.
* man: fix incorrectly placed full stopLennart Poettering2020-08-111-1/+1
|
* man: fix typo in systemd.serviceEtienne Doms2020-08-011-1/+1
|
* tree-wide: drop quotes from around [section]Zbigniew Jędrzejewski-Szmek2020-07-061-5/+5
| | | | | | | For users, the square brackets already serve as markup and clearly delineate the section name from surrounding text. Putting additional markup around that only adds clutter. Also, we were very inconsistent in using the quotes. Let's just drop them altogether.
* tree-wide: fixes for assorted grammar and spelling issuesZbigniew Jędrzejewski-Szmek2020-07-061-1/+1
| | | | Fixes #16363. Also includes some changes where I generalized the pattern.
* tree: wide "the the" and other trivial grammar fixesZbigniew Jędrzejewski-Szmek2020-07-021-1/+1
|
* man: fix various internal referencesZbigniew Jędrzejewski-Szmek2020-06-251-2/+2
| | | | Found with linkchecker.
* core: let user define start-/stop-timeout behaviourJan Klötzke2020-06-091-11/+30
| | | | | | | | | | | | | | | | | | | | | | The usual behaviour when a timeout expires is to terminate/kill the service. This is what user usually want in production systems. To debug services that fail to start/stop (especially sporadic failures) it might be necessary to trigger the watchdog machinery and write core dumps, though. Likewise, it is usually just a waste of time to gracefully stop a stuck service. Instead it might save time to go directly into kill mode. This commit adds two new options to services: TimeoutStartFailureMode= and TimeoutStopFailureMode=. Both take the same values and tweak the behavior of systemd when a start/stop timeout expires: * 'terminate': is the default behaviour as it has always been, * 'abort': triggers the watchdog machinery and will send SIGABRT (unless WatchdogSignal was changed) and * 'kill' will directly send SIGKILL. To handle the stop failure mode in stop-post state too a new final-watchdog state needs to be introduced.
* man: beef up $MAINPID examplesZbigniew Jędrzejewski-Szmek2020-05-261-2/+9
| | | | Inspired by https://github.com/systemd/systemd/pull/15400#discussion_r428537955.
* man: clarify that exit status name mappings are unaffected by SuccessExitStatus=Lennart Poettering2020-05-111-15/+21
| | | | | | | | Fixes: #15757 (Note there's quite some confusion regarding "exit status" vs. "exit code" in the docs here. We should clean this up fully one day. This change tries to fix some occasions of the wrong use, but not all.)
* man: systemd.service: systemd-analyze exit-codes -> exit-statusChris Down2020-05-051-1/+1
| | | | | | | | | 5238d9a83a52 renames this to exit-status, but systemd.service was not updated. The rest of the doc seems a bit inconsistent in its use of the terms "exit code" and "exit status", but it's not that confusing, so leave those alone for now.
* man: sd_notify() race is gone with sd_notify_barrier()Kumar Kartikeya Dwivedi2020-05-011-1/+8
| | | | | | | Add note for change of behaviour in systemd-notify, where parent pid trick is only used when --no-block is passed, and with enough privileges ofcourse. Also, fix a small error in systemd(1).
* tree-wide: fix spelling errorsFrantisek Sumsal2020-04-211-5/+5
| | | | | | Based on a report from Fossies.org using Codespell. Followup to #15436
View Lorry Controller Status