Home
last modified time | relevance | path

Searched refs:relevant (Results 1 – 18 of 18) sorted by relevance

/systemd-251/src/resolve/
DRFCs5 ? = Is this relevant today?
58 Also relevant:
/systemd-251/.github/ISSUE_TEMPLATE/
DBug_report.md39 <!-- Please paste relevant program terminal or journal output here, ideally
/systemd-251/docs/
DJOURNAL_NATIVE_PROTOCOL.md86 dump. After all, log messages are highly relevant for debugging programs, hence
95 actual log message text. Other relevant keys a client should send in most cases
98 information see the [relevant documentation of these
DRESOLVED-VPNS.md96 the last negative reply is used. This means the DNS zones on the relevant
110 is particularly relevant if you have one interface with the `~.` routing domain
183 the configuration to `systemd-resolved.service`? There are three relevant
230 to have everything configured properly (this is particularly relevant when
DDISTRO_PORTING.md93 possible, please maintain the relevant patches downstream.
DUSER_RECORD.md451 use as file system for the user's home directory. This is primarily relevant
457 relevant when the storage mechanism used is `luks`.
461 relevant when the storage mechanism used is `luks`.
465 primarily relevant when the storage mechanism used is `luks`.
831 records it manages. This is particularly relevant to define clearly the context
DENVIRONMENT.md32 `chroot()` environment. This is particularly relevant for systemctl, as it
70 (relevant in particular for the system manager and `systemd-hostnamed`).
DRANDOM_SEEDS.md25 The Linux kernel provides three relevant userspace APIs to request random data
352 systemd's uses are not performance relevant (besides the pool initialization
DCREDENTIALS.md47 is besides first encrypting relevant credentials with one simple command,
DHACKING.md31 run the relevant tool from the build directory.
DPORTABLE_SERVICES.md256 being used under a wrong name and prefix. This is particularly relevant if the
DCONTAINER_INTERFACE.md334 already, if network namespacing is used. Thus it is OK to mount the relevant
DBOOT_LOADER_SPECIFICATION.md237 from `IMAGE_ID=` or `ID=` from `/etc/os-release` of the relevant entry,
DCGROUP_DELEGATION.md45 cgroup v1 too). Specifically two cgroup v2 rules are the most relevant:
/systemd-251/src/home/
Dhomed-manager.c1820 bool relevant = false; in manager_rebalance_calculate() local
1945 relevant = true; in manager_rebalance_calculate()
1959 if (!relevant) { in manager_rebalance_calculate()
/systemd-251/src/boot/efi/
Dmeson.build210 # relevant compiler flags from meson/CFLAGS as povided by the user or distro.
/systemd-251/
DNEWS190 Typically, a better approach to user namespacing in relevant
670 when the relevant keys are pressed for more than 5s. This is useful
957 whether to use the relevant fields from the IPv6 Router Advertisement
2528 where the device starts being relevant, and those where it stops
2529 being relevant (the latter now regularly happening due to the new
2563 uevents actions (i.e. considering devices only relevant after "add"
2566 devices relevant after all event types, except for "remove", which
2568 should be considered relevant on "unbind", even though conceptually
2571 considered relevant even after "unbind", however I/O errors
2575 relevant or not most likely needs to be updated to use the new
[all …]
DTODO1015 * In DynamicUser= mode: before selecting a UID, use disk quota APIs on relevant
1066 on PID 1 with the relevant signals, and makes relevant files in /sys and