| /systemd-251/src/shared/ |
| D | barrier.c | 103 b->them = eventfd(0, EFD_CLOEXEC | EFD_NONBLOCK); in barrier_create()
104 if (b->them < 0) in barrier_create()
132 b->them = safe_close(b->them); in barrier_destroy()
167 SWAP_TWO(b->me, b->them); in barrier_set_role()
218 { .fd = b->them, in barrier_read()
233 len = read(b->them, &buf, sizeof(buf)); in barrier_read()
|
| D | barrier.h | 32 int them; member
|
| /systemd-251/docs/ |
| D | CODE_QUALITY.md | 15 no privileges are available, hence consider also running them with `sudo
19 build them too with `meson setup -Dslow-tests=true`. (Note that there are a
26 them in nspawn and qemu. Requires root.
33 `./tools/find-double-newline.sh recpatch` to fix them. Take this with a grain
38 `./tools/find-tabs.sh recpatch` to fix them. (Again, grain of salt, foreign
|
| D | USERDB_AND_DESKTOPS.md | 32 ability that access to them can be suspended automatically during system sleep,
35 but most of the time just suspend them instead. Previously, the encryption keys
37 sufficiently equipped attackers could read them from there and gain full access
48 It is suggested that desktop environments that implement lock screens run them
78 any user management UI to expose them directly.
136 them. While I (Lennart) personally believe in the long run `systemd-homed` is
142 records via `accounts-daemon`, so that clients of the latter can consume them
157 learn them natively. Fields for other authentication mechanisms, such as
|
| D | TEMPORARY_DIRECTORIES.md | 39 for them, like X11 does with `/tmp/.X11-unix/` through `tmpfiles.d/`
99 operate on open, and only access the files through them. This way it doesn't
103 files right after creating them to ensure that on unexpected program
120 algorithm will skip all directories (and everything below them) that are
125 when the program that owns them dies, but not while it is still running. Use
137 looks at the access time of files when deciding whether to delete them, it's
146 the sticky bit has a different meaning for them.
185 2. `unlink()` temporary files right after creating them. This is very similar
187 creating them, while keeping open a file descriptor to them. Unlike
|
| D | CGROUP_DELEGATION.md | 36 the basic concepts still fully apply. You should read them too, if you do something
58 different processes managing them. However, only a single process should own a
119 no controller usage is required for them). The fact that systemd keeps these
127 thinking about them as orthogonal won't help you in the long run anyway.
156 them as a unit. Unlike services, scopes can only be declared and started
212 property of your program, systemd won't touch them — all attributes of *those*
248 to them. If we'd allow delegation on slice units then this would mean that
260 was delegated to them. Note that this is only supported on kernels 5.6 and
365 for grabs: systemd won't manage them, and hence won't delegate them to your
368 decide to use them, then that's fine, but systemd won't help you with it (but
[all …]
|
| D | RANDOM_SEEDS.md | 18 entropy pool combines various entropy inputs together, mixes them and provides
80 they usually do not credit entropy for them.
120 * systemd maintains various hash tables internally. In order to harden them
270 days. Consider using them while crediting
277 test environments. Tough luck. Talk to your hosting provider, and ask them
355 certainly make use of them where appropriate.
379 similar for them. Ideally, we'd have an official way to pass such a seed as
410 hence we shouldn't write them too often. Writing them once during
411 installation should generally be OK, but rewriting them on every single
|
| D | CODING_STYLE.md | 25 you automatically, if you let them (as well as a few other things). Please
94 expressions, and align them vertically. Define both an enum and a type for
143 in them. Instead of doing a lot of locking for that, we tend to prefer using
175 safe to include them in any order possible. However, to not clutter global
184 them make sure they are static at least, instead of exported. Especially in
188 the code using them has side-effects make programs non-transparent. That
201 incompatible with glibc it's on them. However, if there are equivalent POSIX
316 `free()` works, which accepts `NULL` pointers and becomes a NOP for them. By
472 better behavior in this case, so consider using them as an alternative.)
653 them. `F_DUPFD_CLOEXEC` with `3` as parameter avoids them.
|
| D | UIDS-GIDS.md | 46 the UIDs 0 and 65534 if the system user database doesn't list them. This means
105 attempted to make UID assignments stable, by deriving them from a hash of
117 if you write them in hexadecimal, they might make more sense: 0xEF00 and
132 these numbers, consider them in hexadecimal: 0x00080000…0x6FFFFFFF. This
149 them. Also note that while the allocation logic is operating, the glibc
245 then map them to a higher UID range for use in user namespacing via another
302 makes them available during early boot too (i.e. before networking is
|
| D | AUTOMATIC_BOOT_ASSESSMENT.md | 170 considered successful, simply place them in units (if they aren't already)
171 and order them before the generic `boot-complete.target` target unit,
179 wrap them in a unit and order them after `boot-complete.target`, pulling it
|
| D | PORTABILITY_AND_STABILITY.md | 10 …the first version released with Fedora 15) we promise to keep a number of them stable and compatib…
20 … only for early boot and late shutdown, with very few exceptions. To list them here: `basic.target…
51 …ut leave out all components except the ones you are interested in and run them without the core of…
73 …hese interfaces are our invention (but most), we just adopted them in systemd to make them more pr…
133 …o eventually document all interfaces we defined. If we haven't documented them for now, this is us…
|
| D | CONTAINER_INTERFACE.md | 51 for them for which it needs to be able to create these device nodes.
177 these and pass them on to the container's init process, also setting
291 mount namespaces and the mount certain file systems into them. You break all
298 you cannot link them to each other.
328 device management is properly available on the instance. Among them
344 by dropping them you ensure that you get an entirely clean boot, as systemd
372 than with them around.
377 and having capabilities inside a container doesn't mean one also has them
|
| D | PREDICTABLE_INTERFACE_NAMES.md | 16 …them: this required a writable root directory which is generally not available; the statelessness …
18 …d fixed slot topology information in certain firmware interfaces and uses them to assign fixed nam…
|
| /systemd-251/ |
| D | TODO | 5 them when parsing config.
118 optionally sign them. for that we should extend our syntax for specifying pcr
201 into (even if we hardcode them)
215 EFI kernel, for sd-stub to pick them up. These creds should be locked to
218 place them next to EFI kernel, for sd-stub to pick them up.
432 encode a version as well as assessment counters, and then mount them into the
465 credential logic and drops them into /run where nss-systemd can pick them up,
580 system paths at service startup time and pass them to the service process via
584 * Similar, ConnectStream= which takes IP addresses and connects to them.
766 arbitrary processes, regardless of the priority we want to watch them with,
[all …]
|
| D | .gitattributes | 5 # Mark files as "generated", i.e. no license applies to them.
|
| /systemd-251/src/rpm/ |
| D | meson.build | 12 # The last two don't get installed anywhere, one of them needs to included in
|
| /systemd-251/hwdb.d/ |
| D | README | 6 man:systemd-hwdb(8) compiles them into a binary database.
|
| /systemd-251/test/test-execute/ |
| D | exec-temporaryfilesystem-options.service | 9 # Let's override some of them, and test "ro".
|
| /systemd-251/test/test-path/ |
| D | basic.target | 11 # remote-fs.target by default, hence pull them in explicitly here. Note that we
|
| /systemd-251/units/ |
| D | systemd-journal-gatewayd.service.in | 36 # If there are many split up journal files we need a lot of fds to access them
|
| D | basic.target | 18 # remote-fs.target by default, hence pull them in explicitly here. Note that we
|
| D | systemd-journal-upload.service.in | 38 # If there are many split up journal files we need a lot of fds to access them
|
| D | systemd-journal-remote.service.in | 41 # If there are many split up journal files we need a lot of fds to access them
|
| D | systemd-journald-dev-log.socket | 32 # for receiving syslog messages, and for forwarding them to any other
|
| /systemd-251/test/units/ |
| D | basic.target | 18 # remote-fs.target by default, hence pull them in explicitly here. Note that we
|