summaryrefslogtreecommitdiff
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
* boot-loader-spec: add devicetree-overlay keyMichael Tretter2019-10-291-0/+6
| | | | | | | | | | | | | Device tree overlays are a convenient way to patch device trees, e.g., add new devices to a device tree or enable/disable devices. This is useful for non-discoverable but configurable hardware. Device tree overlays are commonly used for displays on the Raspberry Pi or for describing the content of FPGA bitstreams. Add the devicetree-overlay key to boot loader specification entries to allow boot loaders to apply overlays. See #13537
* Merge pull request #13423 from pwithnall/12035-session-time-limitsZbigniew Jędrzejewski-Szmek2019-10-281-0/+1
|\ | | | | Add `RuntimeMaxSec=` support to scope units (time-limited login sessions)
| * scope: Support RuntimeMaxSec= directive in scope unitsPhilip Withnall2019-10-281-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | Just as `RuntimeMaxSec=` is supported for service units, add support for it to scope units. This will gracefully kill a scope after the timeout expires from the moment the scope enters the running state. This could be used for time-limited login sessions, for example. Signed-off-by: Philip Withnall <withnall@endlessm.com> Fixes: #12035
* | docs: fix inadvertent change in uid rangeZbigniew Jędrzejewski-Szmek2019-10-061-1/+1
| | | | | | | | https://github.com/systemd/systemd/commit/a305eda35f18fbacc771cc1582b688d60890a9d2#r35378755
* | Merge pull request #13246 from keszybz/add-SystemdOptions-efi-variableZbigniew Jędrzejewski-Szmek2019-10-031-4/+7
|\ \ | | | | | | Add efi variable to augment /proc/cmdline
| * | Add support for SystemdOptions EFI var to augment /proc/cmdlineZbigniew Jędrzejewski-Szmek2019-09-161-4/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In various circumstances, overriding the kernel commandline can be inconvenient. People have different bootloaders, and e.g. the grub config can be pretty scary. grubby helps, but it isn't always available. This option adds an alternative mechanism that can quite convenient on EFI systems. cmdline settings have higher priority, because they can be (usually) changed on the bootloader prompt. $SYSTEMD_EFI_OPTIONS can be used to override, same as $SYSTEMD_PROC_CMDLINE.
* | | nspawn: rename UNIFIED_CGROUP_HIERARCHY to SYSTEMD_NSPAWN_UNIFIED_HIERARCHYZbigniew Jędrzejewski-Szmek2019-10-011-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We should never have used an unprefixed environment variable name. All other systemd-nspawn variables have the "SYSTEMD_NSPAWN_" prefix, and all other systemd variables have the "SYSTEMD_" prefix. The new variable name takes precedence, but we fall back to checking the old one. If only the old one is found, a warning is emitted. In addition, SYSTEMD_NSPAWN_UNIFIED_HIERARCHY="" is accepted as an override to avoid looking for the old variable name. We have a variable with the same name ($UNIFIED_CGROUP_HIERARCHY) in tests, which governs both systemd-nspawn and qemu behaviour. It is not renamed.
* | | cgroup: introduce support for cgroup v2 CPUSET controllerPavel Hrdina2019-09-241-0/+2
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | Introduce support for configuring cpus and mems for processes using cgroup v2 CPUSET controller. This allows users to limit which cpus and memory NUMA nodes can be used by processes to better utilize system resources. The cgroup v2 interfaces to control it are cpuset.cpus and cpuset.mems where the requested configuration is written. However, it doesn't mean that the requested configuration will be actually used as parent cgroup may limit the cpus or mems as well. In order to reflect the real configuration cgroup v2 provides read-only files cpuset.cpus.effective and cpuset.mems.effective which are exported to users as well.
* | docs: fix push recipe in RELEASE.mdZbigniew Jędrzejewski-Szmek2019-09-051-1/+1
| |
* | docs: fix typo in boot loader docnikolas2019-09-051-1/+1
| |
* | docs: create new SECURITY.md pageZbigniew Jędrzejewski-Szmek2019-08-302-2/+9
| | | | | | | | | | github has special support for that name: https://help.github.com/en/articles/adding-a-security-policy-to-your-repository.
* | docs: new systemd-security mailing listZbigniew Jędrzejewski-Szmek2019-08-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the past, we asked people to open a security bug on one of the "big" distros. This worked OK as far as getting bugs reported and notifying some upstream developers went. But we always had trouble getting information to all the appropriate parties, because each time a bug was reported, a big thread was created, with a growing CC list. People who were not CCed early enough were missing some information, etc. To clean this up, we decided to create a private mailing list. The natural place would be freedesktop.org, but unfortunately the request to create a mailing list wasn't handled (https://gitlab.freedesktop.org/freedesktop/freedesktop/issues/134). And even if it was, at this point, if there was ever another administrative issue, it seems likely it could take months to resolve. So instead, we asked for a list to be created on the redhat mailservers. Please consider the previous security issue reporting mechanisms rescinded, and send any senstive bugs to systemd-security@redhat.com.
* | docs: fix env var name in random seed markdown documentationLennart Poettering2019-08-111-6/+6
| |
* | docs: fix typoSimon Schricker2019-07-301-1/+1
|/
* docs: add longer document about systemd and random number seedsLennart Poettering2019-07-251-0/+418
|
* docs: document new random seed EFI vars as part of the boot loader interfaceLennart Poettering2019-07-251-1/+25
|
* core: ExecCondition= for servicesAnita Zhang2019-07-171-0/+1
| | | | Closes #10596
* locale-util: suppress non-UTF-8 locales when enumerating themLennart Poettering2019-07-141-0/+6
| | | | | | | | | | | | | | Let's hide non-UTF-8 locales by default. It's 2019 after all. Let's add an undocumented env var to reenable listing them though. This should substantially shorten the list of choices we offer users, and only show realistic choices. note that only firstboot and localectl make use of this information, and both allow configuration of values outside of these lists, hence all this change does is hide legacy options, but they are still available if you know what you do, and that's how it should be.
* meson: drop varlogdir variableZbigniew Jędrzejewski-Szmek2019-07-043-33/+27
| | | | | | | | It was only used for exactly one thing: to substitute in the text in /var/log/README. But it's use there was completely wrong, because the text talks about "missing" log files from syslog, so even if we configured systemd to log to a different directory, the "missing" log files would still be "missing" from the old location.
* meson: create /var/log/journal/{,remote/} conditionallyZbigniew Jędrzejewski-Szmek2019-07-041-1/+1
| | | | | | | | | | Not everybody has those dirs in the filesystem (and they don't need to). When creating an installation package using $DESTDIR, it is easy enough to remove or ignore those directories, but if installing into a real root, it is ugly to create and remove them. Let's add an option so people can skip it if they want. Inspired by #12930.
* docs: fix typos and duplicate wordsMichael Prokop2019-06-274-4/+4
| | | | | | | | | s/and and/and/ s/explicity/explicitly/ s/that that/that/ s/the the/the/ s/is is/it is/ s/overriden/overridden/
* some CODING_STYLE additionsLennart Poettering2019-06-251-0/+13
|
* docs: CGROUP_DELEGATION: fix a typo in "that"Jan Pokorný2019-06-181-1/+1
|
* Continuous Fuzzing Integration with FuzzitJeka Pats2019-06-141-2/+6
| | | | | | | | | | includes two travis ci steps: 1) Every pull-request/push all fuzzing targets will do a quick sanity run on the generated corpus and crashes (via Fuzzit) 2) On a daily basis the fuzzing targets will be compiled (from master) and will and their respectible fuzzing job on Fuzzit will be updated to the new binary.
* docs: add documentation for sanitizersFrantisek Sumsal2019-05-272-0/+93
|
* Drop support for /usr/sbin/halt.localMichael Biebl2019-05-231-1/+0
| | | | | /usr/sbin/halt.local is a Fedora/Red Hat anachronism from pre-systemd times.
* 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
|
View Lorry Controller Status