summaryrefslogtreecommitdiff
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
...
* docs: add comment about high 32bit range and signed uidsLennart Poettering2019-05-161-1/+9
|
* cgroup: Polish hierarchically aware protection docs a bitChris Down2019-05-081-0/+1
| | | | | | | I missed adding a section in `systemd.resource-control` about DefaultMemoryMin in #12332. Also, add a NEWS entry going over the general concept.
* codespell: fix spelling errorsBen Boeckel2019-04-291-1/+1
|
* core: support DisableControllers= for transient unitsAnita Zhang2019-04-221-0/+1
|
* Merge pull request #12296 from poettering/coding-style-sectionsYu Watanabe2019-04-131-362/+373
|\ | | | | split CODING_STYLE document into multiple thematic sections
| * CODING_STYLE: rename "Others" section to "Code Organization and Semantics"Lennart Poettering2019-04-121-37/+33
| | | | | | | | | | This is a bit of a grabbag, but it's the best I could come up with without having lots of single-item sections.
| * CODING_STYLE: split out section about runtime behaviourLennart Poettering2019-04-121-31/+33
| |
| * CODING_STYLE: add section about C constructs useLennart Poettering2019-04-121-74/+72
| |
| * CODING_STYLE: split out section about deadlocksLennart Poettering2019-04-121-8/+9
| |
| * CODING_STYLE: split out section about loggingLennart Poettering2019-04-121-28/+29
| |
| * CODING_STYLE: export section about exporting symbolsLennart Poettering2019-04-121-17/+19
| |
| * CODING_STYLE: split out section about destructorsLennart Poettering2019-04-121-23/+25
| |
| * CODING_STYLE: split out section about command line parsingLennart Poettering2019-04-121-12/+13
| |
| * CODING_STYLE: Split out section about error handlingLennart Poettering2019-04-121-52/+52
| |
| * CODING_STYLE: split out section about commiting to gitLennart Poettering2019-04-121-7/+8
| |
| * CODING_STYLE: split out section about file descriptorsLennart Poettering2019-04-121-23/+24
| |
| * CODING_STYLE: split out section about memory allocationsLennart Poettering2019-04-121-32/+32
| |
| * CODING_STYLE: move out section about TypesLennart Poettering2019-04-121-35/+35
| |
| * CODING_STYLE: add section about how to reference specific conceptsLennart Poettering2019-04-121-0/+2
| |
| * CODING_STYLE: split out bits about Formatting into its own sectionLennart Poettering2019-04-121-49/+52
| | | | | | | | (And, for now, add a section "Other" to separate the rest of the stuff)
| * CODING_STYLE: add a section about functions not to useLennart Poettering2019-04-121-37/+38
| | | | | | | | | | Let's add sections to the document. First off, let's add one about functions not to use.
* | service: handle abort stops with dedicated timeoutJan Klötzke2019-04-121-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When shooting down a service with SIGABRT the user might want to have a much longer stop timeout than on regular stops/shutdowns. Especially in the face of short stop timeouts the time might not be sufficient to write huge core dumps before the service is killed. This commit adds a dedicated (Default)TimeoutAbortSec= timer that is used when stopping a service via SIGABRT. In all other cases the existing TimeoutStopSec= is used. The timer value is unset by default to skip the special handling and use TimeoutStopSec= for state 'stop-watchdog' to keep the old behaviour. If the service is in state 'stop-watchdog' and the service should be stopped explicitly we still go to 'stop-sigterm' and re-apply the usual TimeoutStopSec= timeout.
* | cgroup: Implement default propagation of MemoryLow with DefaultMemoryLowChris Down2019-04-121-0/+1
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In cgroup v2 we have protection tunables -- currently MemoryLow and MemoryMin (there will be more in future for other resources, too). The design of these protection tunables requires not only intermediate cgroups to propagate protections, but also the units at the leaf of that resource's operation to accept it (by setting MemoryLow or MemoryMin). This makes sense from an low-level API design perspective, but it's a good idea to also have a higher-level abstraction that can, by default, propagate these resources to children recursively. In this patch, this happens by having descendants set memory.low to N if their ancestor has DefaultMemoryLow=N -- assuming they don't set a separate MemoryLow value. Any affected unit can opt out of this propagation by manually setting `MemoryLow` to some value in its unit configuration. A unit can also stop further propagation by setting `DefaultMemoryLow=` with no argument. This removes further propagation in the subtree, but has no effect on the unit itself (for that, use `MemoryLow=0`). Our use case in production is simplifying the configuration of machines which heavily rely on memory protection tunables, but currently require tweaking a huge number of unit files to make that a reality. This directive makes that significantly less fragile, and decreases the risk of misconfiguration. After this patch is merged, I will implement DefaultMemoryMin= using the same principles.
* CODING_STYLE: adjust indentation rules, and add note about config loadingZbigniew Jędrzejewski-Szmek2019-04-121-3/+5
|
* docs: also document updates to stable repoZbigniew Jędrzejewski-Szmek2019-04-031-0/+1
|
* docs: let's not close the milestone earlyZbigniew Jędrzejewski-Szmek2019-04-031-1/+1
|
* docs: update release steps for mesonZbigniew Jędrzejewski-Szmek2019-04-031-8/+10
|
* docs: fix path to unit filesLennart Poettering2019-04-031-11/+11
|
* man: document the new RestrictSUIDSGID= settingLennart Poettering2019-04-021-0/+1
|
* core: optionally, trigger .timer units on timezone and clock changesLennart Poettering2019-04-021-1/+3
| | | | Fixes: #6228
* docs: adjust the spec a bit with firmware authros in mindLennart Poettering2019-03-141-7/+36
| | | | | | | | This borrows heavily from Nico Huber's https://github.com/systemd/systemd/pull/10398, but makes a number of changes. Replaces: #10398
* docs: comprehensively document what a minimal portable service image needs ↵Lennart Poettering2019-03-141-7/+32
| | | | | | | | to include The docs were incomplete on this. Let's fix that. Fixes: #11870
* docs: document the new environment variables logind groksLennart Poettering2019-03-051-0/+45
|
* docs: add a note about compilation optionsZbigniew Jędrzejewski-Szmek2019-03-051-0/+14
| | | | Closes #6371.
* xbootldr: multiple spaces between keys and values (#11872)Ben Iofel2019-03-031-1/+1
| | | The example below the changed line has multiple spaces between e.g. `title` and `Fedora`
* docs: enclose all uuids in ``Lennart Poettering2019-03-011-3/+3
|
* Fix typo - "do note use guessable names"unixsysadmin2019-02-201-1/+1
| | | Fix typo - "do note use guessable names" to "do not use guessable names"
* docs: document semantics of /tmp and /var/tmpLennart Poettering2019-02-201-0/+220
|
* Merge pull request #9594 from filbranden/cpu_quota_period1Lennart Poettering2019-02-151-0/+1
|\ | | | | core: add CPUQuotaPeriodSec=
| * core: add CPUQuotaPeriodSec=Filipe Brandenburger2019-02-141-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This new setting allows configuration of CFS period on the CPU cgroup, instead of using a hardcoded default of 100ms. Tested: - Legacy cgroup + Unified cgroup - systemctl set-property - systemctl show - Confirmed that the cgroup settings (such as cpu.cfs_period_ns) were set appropriately, including updating the CPU quota (cpu.cfs_quota_ns) when CPUQuotaPeriodSec= is updated. - Checked that clamping works properly when either period or (quota * period) are below the resolution of 1ms, or if period is above the max of 1s.
* | resolved: use Cloudflare public DNS server as a default fallback alongside ↵Ignat Korchagin2019-02-151-2/+2
|/ | | | | | | | Google one Cloudflare public DNS service is currently the fastest one according to https://www.dnsperf.com/#!dns-resolvers. Why not improve the experience for systemd users using this as a default fallback nameserver?
* portable: document /etc/machine-id and /etc/resolv.confДамјан Георгиевски2019-02-041-4/+8
| | | | | | | | … requirement for portable service images. systemd will mount the host machine-id and resolv.conf at these locations, so for read-only images these must exist in the image, because they can't be created.
* CODING_STYLE: fix grammar mistakeChris Morin2019-01-171-2/+2
|
* Merge pull request #11317 from filbranden/docs1Zbigniew Jędrzejewski-Szmek2019-01-0319-18/+81
|\ | | | | Improvements to systemd.io generation
| * docs: generate index.md in JekyllFilipe Brandenburger2019-01-021-18/+5
| | | | | | | | | | | | | | | | | | | | This uses a {% for %} loop in Jekyll to render the page, from the "title" information in the Front Matter of the actual page files. This also makes `make-index-md` build rule unnecessary, since generation is done by the template engine itself. Tested this by running Jekyll locally.
| * docs: add a "front matter" snippet to our markdown pagesFilipe Brandenburger2019-01-0219-0/+76
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It turns out Jekyll (the engine behind GitHub Pages) requires that pages include a "Front Matter" snippet of YAML at the top for proper rendering. Omitting it will still render the pages, but including it opens up new possibilities, such as using a {% for %} loop to generate index.md instead of requiring a separate script. I'm hoping this will also fix the issue with some of the pages (notably CODE_OF_CONDUCT.html) not being available under systemd.io Tested locally by rendering the website with Jekyll. Before this change, the *.md files were kept unchanged (so not sure how that even works?!), after this commit, proper *.html files were generated from it.
* | cgroup: s/cgroups? ?v?([0-9])/cgroup v\1/gIChris Down2019-01-031-33/+33
|/ | | | | | | | | | Nitpicky, but we've used a lot of random spacings and names in the past, but we're trying to be completely consistent on "cgroup vN" now. Generated by `fd -0 | xargs -0 -n1 sed -ri --follow-symlinks 's/cgroups? ?v?([0-9])/cgroup v\1/gI'`. I manually ignored places where it's not appropriate to replace (eg. "cgroup2" fstype and in src/shared/linux).
* remount-fs: optionally remount / writable, if we are told through an env varLennart Poettering2018-12-181-0/+8
|
* docs: add missing section to ENVIRONMENT.mdLennart Poettering2018-12-171-0/+2
| | | | | No, this is not an env var understood by logind. Let's fix the confusoin.
* tree-wide: s/time-out/timeout/gZbigniew Jędrzejewski-Szmek2018-12-141-3/+3
| | | | | | | | | | | | | | | | | From WordNet (r) 3.0 (2006) [wn]: time-out n 1: a brief suspension of play; "each team has two time-outs left" From The Free On-line Dictionary of Computing (18 March 2015) [foldoc]: timeout A period of time after which an error condition is raised if some event has not occured. A common example is sending a message. If the receiver does not acknowledge the message within some preset timeout period, a transmission error is assumed to have occured.
View Lorry Controller Status