summaryrefslogtreecommitdiffstats
path: root/sysusers.d (unfollow)
Commit message (Collapse)AuthorFilesLines
2020-01-21core: show the UID we cannot parseLennart Poettering1-1/+1
2020-01-21json: lower maximum allowed recursion to 2KLennart Poettering1-3/+9
Apparently 4K is too high still, let's halve it. Fixes: #14396
2020-01-20test: add test for https://github.com/systemd/systemd/issues/14560Lennart Poettering3-0/+12
2020-01-20core: make sure StandardInput=file: doesn't get dup'ed to stdout/stderr by ↵Lennart Poettering1-12/+25
default Fixes: #14560
2020-01-20units: drop full paths for utilities in $PATHZbigniew Jędrzejewski-Szmek27-78/+65
This makes things a bit simpler and the build a bit faster, because we don't have to rewrite files to do the trivial substitution. @rootbindir@ is always in our internal $PATH that we use for non-absolute paths, so there should be no functional change.
2020-01-20Italian: language updateDaniele Medri1-15/+164
2020-01-18pkgconf: add full generator pathsSascha Dewald1-0/+2
2020-01-18tree-wide: we forgot to destroy some bus errorsLennart Poettering2-2/+2
2020-01-18typo: "May modify to" -> "May modify"Wieland Hoffmann1-1/+1
2020-01-17mount: make checks on perpetual mount units more laxLennart Poettering1-4/+3
We don#t really care where perpetual mounts are mounted from, since they have to exist since before we run anyway.
2020-01-17core: never allow perpetual units to be maskedLennart Poettering1-1/+3
Fixes: #14550
2020-01-17man: document that WakeSystem= affects clock choiceLennart Poettering1-2/+14
Fixes: #8308
2020-01-17docs: uppercase are headersLennart Poettering1-1/+1
We do this in most cases, do so here too.
2020-01-17docs: let's reduce our spurious whitespace a bitLennart Poettering1-2/+0
2020-01-17docs: in PORTABILITY_AND_STABILITY only use one h1Lennart Poettering1-2/+2
According to the designer of the page layout a page only should have one h1 header, and everything else should be h2, h3, … I think that makes a ton of sense, hence let's downgrade some headers here.
2020-01-17man: clarify that user rlimits cannot go beyond limits set for service mgrLennart Poettering2-53/+46
Fixes: #10758
2020-01-17man: extend on halt documentationLennart Poettering1-9/+11
Based on the suggestions on #13254 and #13264 Fixes: #13254
2020-01-17man: document that rootflags= does not override /etc/fstabLennart Poettering1-3/+7
Fixes: #13324
2020-01-17man: underline that AccuracySec= is about coalescing timer events, nothing elseLennart Poettering1-1/+7
Fixes: #13328
2020-01-17man: mention that Before= doesn't work for device unitsLennart Poettering1-1/+5
Fixes: #13362
2020-01-17man: suggest SYSTEMD_WANTS usage instead of RUN for long running processesLennart Poettering1-0/+4
Fixes: #14259
2020-01-17man: document the limits of the block device discovery for IO cgroup optionsLennart Poettering1-0/+14
Fixes: #14271
2020-01-17man: document how error propagation to path units worksLennart Poettering1-0/+9
Fixes: #14331
2020-01-17man: document that program invocation will fail if the User= does not existLennart Poettering1-6/+7
Fixes: #14565
2020-01-17docs: clarify that we don't want to own $BOOT exclusivelyLennart Poettering1-0/+14
Let's be clearer here. Prompted by a quick discussion I had with @gicmo.
2020-01-17core: reduce indentation a bitZbigniew Jędrzejewski-Szmek1-16/+16
2020-01-17logind: use loop instead of repeated codeZbigniew Jędrzejewski-Szmek1-28/+16
https://github.com/systemd/systemd/pull/14096#discussion_r350953689
2020-01-17shared/user-record-nss: use macro to avoid repeatsZbigniew Jędrzejewski-Szmek1-63/+46
It's easier to read when each field is intialized in exactly one place.
2020-01-16shared/user-record-nss: shorten code a bitZbigniew Jędrzejewski-Szmek1-21/+10
free_and_strdup() already does comparison internally.
2020-01-16Disable reading SystemdOptions EFI Var when in SecureBoot modeArian van Putten5-51/+66
In SecureBoot mode this is probably not what you want. As your cmdline is cryptographically signed like when using Type #2 EFI Unified Kernel Images (https://systemd.io/BOOT_LOADER_SPECIFICATION/) The user's intention is then that the cmdline should not be modified. You want to make sure that the system starts up as exactly specified in the signed artifact.
2020-01-16Clarify journald.conf MaxLevelStore documentationLuca Boccassi1-3/+3
'stored on disk' gives the impression that this option affects only permanent storage, even though it affects everything the journal records, regardless of the storage type. Use 'stored in the journal' to avoid confusion.
2020-01-16sysctl: downgrade message when we have no permissionZbigniew Jędrzejewski-Szmek1-7/+10
We need to run sysctl also in containers, because the network subtree is namespaces and may legitimately be writable. But logging all "errors" at notice level creates unwanted noise. Also downgrade message about missing sysctls to log_info. This might also be relatively common when configuration is targeted at different kernel versions. With log_debug it'll still end up in the logs, but isn't really worth of "notice" most of the time. https://bugzilla.redhat.com/show_bug.cgi?id=1609806
2020-01-16sysctl: move hashmap allocation out of main functionZbigniew Jędrzejewski-Szmek1-10/+9
This allocation is a low level detail, and it seems nicer to keep it out of run().
2020-01-16man: rework section about configuration file precedenceZbigniew Jędrzejewski-Szmek1-41/+37
This section is loaded in a bunch of places, so this affects many man pages. 1. point the reader to the synopsis section, which has the exact paths that are used to load files. 2. put the "reference" part first, and recommendations later, in separate paragraphs. 3. describe how individual settings and whole files are replaces. Closes #12791.
2020-01-15core: on each iteration processing /proc/self/mountinfo merge all discovery ↵Lennart Poettering1-3/+16
flags for each path This extends on d253a45e1c147f5174265d71d7419da7bd52a88b, and instead of merging just a single flag from previous mount entries of /proc/self/mountinfo for the same path we merge all three. This shouldn't change behaviour, but I think make things more readable. Previously we'd set MOUNT_PROC_IS_MOUNTED unconditionally, we still do. Previously we'd inherit MOUNT_PROC_JUST_MOUNTED from a previous entry on the same line, we still do. MOUNT_PROC_JUST_CHANGED should generally stay set too. Why that? If we have two mount entries on the same mount point we'd first process one and then the other, and the almost certainly different mount parameters of the two would mean we'd set MOUNT_PROC_JUST_CHANGED for the second. And with this we'll definitely do that still. This also adds a comment explaining the situation a bit, and why we get into this situation.
2020-01-15execute: allow pam_setcred() to fail, ignore errorsLennart Poettering1-1/+1
Fixes: #14567 Alternative-To: #14569
2020-01-15execute: add const to array parameters, where possibleLennart Poettering1-2/+2