| Commit message (Collapse) | Author | Files | Lines |
|---|
|
```
In file included from ../src/nsresourced/nsresourced-manager.c:9:
../src/shared/bpf-link.h:5:10: fatal error: bpf/libbpf.h: No such file or directory
5 | #include <bpf/libbpf.h>
| ^~~~~~~~~~~~~~
```
Follow-up for 46718d344fdaaaf523d854a0c728197e7406a55a
|
|
The functionality was explicitly not included in 6.11 for some
unknown reason so drop the logic from systemd-repart as well so
we don't release v257 with it included.
|
|
Otherwise, `<variable>$BOOT</variable>` is rendered:
```
[2548/2992] Generating man/repart.d.5 with a custom command
Element variable in namespace '' encountered in para, but no template matches.
Element variable in namespace '' encountered in para, but no template matches.
```
|
|
Signed-off-by: Marius Hoch <mail@mariushoch.de>
|
|
|
|
main pid and control pid is captured
If `Delegate` is configured in service, cgroup agent will never send out
any datagram as .control subcgroup is generated. Thus systemd will watch
all processes on the cgroup hierarchy for SIGCHLD to deal with unreliable
cgroup notifications.
In this way, systemd should rewatch all processes when any SIGCHLD is
captured, more than the control pid or main pid.
|
|
SetShowStatus() was added in order to fix #11447. Recently, I ran into
the exact same problem that OP was experiencing in #11447. I wasn’t able
to figure out how to deal with the problem until I found #11447, and it
took me a while to find #11447.
This commit takes what I learned from reading #11447 and adds it to the
documentation. Hopefully, this will make it easier for other people who
run into the same problem in the future.
|
|
Fixes #34459.
|
|
To support the case that paths to plugins contain spaces.
Prompted by #34459
|
|
Fixes db15657dfb8100c3c6cd8cf60fa68521e019d47a
|
|
This prints a python data structure which we shouldn't do during
normal operation.
|
|
No functional change, just refactoring.
|
|
The test cannot run with the bash test runner, as it requires python.
Hence, test.sh is not necessary.
Follow-up for a37640653cab108bb2cfdcba7e9422cced925e95.
|
|
Follow-up for a37640653cab108bb2cfdcba7e9422cced925e95.
|
|
This mirrors the behavior of `systemd-firstboot` and allows bootup
messages to settle down before user input is actually processed.
See: https://github.com/systemd/systemd/issues/34448
|
|
|
|
Previously, if an file cannot be opened, e.g. due to its permission,
config_parse_many() or so did not log the error even if CONFIG_PARSE_WARN
flag is set. This makes all error paths in these functions are logged,
and the log level is controlled by the flag.
Prompted by #34436.
|
|
|
|
This was designed to deal with $BOOT, as defined by the Boot Loader
Specification, but it was made a generic mechanism because it is useful
elsewhere too. See the updated man page for usage examples, motivation,
and an explanation of how this works.
|
|
Fixes an oversight in `context_allocate_partitions` that makes it
succeed in cases where it should fail. Essentially, there was nothing
actually enforcing SizeMinBytes= and PaddingMinBytes= for partitions
that exist, only for new partitions. This behavior is inconsistent with
the docs, which state that existing partitions will be grown to at least
the specified minimum size, and that "If the backing device does not
provide enough space to fulfill the constraints placing the partition
will fail".
|
|
The macro didn't properly parenthesize a caller-controlled argument.
For example: `STRV_FOREACH_PAIR(a, b, something ?: something_else)`
would expand to `typeof(*something ?: something_else)`, which would
cause compile failures
|
|
|
|
|
|
When an interface enters unmanaged state, there are two possibilities:
- no matching .network file found,
- found a matching .network with Unmanaged=yes.
When a matching .network file is found, networkd logs the filename.
Let's also log when no matching .network file is found.
This also slightly adjust the log message when a matching .network file
found.
Closes #34436.
|
|
The error code `r` from the read function is being logged, but the error code `rc` from the table data insertion function should be logged instead.
|
|
|
|
This tests the whole shebang:
1. That ukify can generate them properly
2. That systemd-boot can dissect them properly
3. That systemd-stub can accept profile selection propery
4. That the profile information ends up in /run/systemd/stub/ properly
5. That systemd-measure correctly calculates the expected PCR 11 values
for each profile and that we can unlock a public-key bound LUKS
volume with it
|
|
|
|
Follow-up for 27cacec939a46f61706d7b48a51b6f5880be4662.
|
|
log_setup() overrides the previously set log target again so we
can't use it in log_setup_generator().
Follow-up for aa976d87889ae22b7347787a1ebd03a31dcc0a9e
|
|
|
|
|
|
When eBPF is disabled, the hashmap will be never used. Let's not
allocate it.
|
|
Previously, manager_free() did not assign NULL to Manager.sysctl_shadow,
hence sysctl_clear_link_shadows() called by link_free() will causes
use-after-free. To fix the issue, this makes Manager.sysctl_shadow will be
set to NULL after it is freed,
Fixes a bug introduced by 6d9ef22acdeac4b429efb75164341233955484af.
|
|
- rename rootcg -> root_cgroup_fd, to emphasize it is a fd,
- drop nested function call, and check error code.
|
|
Then, replace rb_free() in networkd.
Follow-up for 6d9ef22acdeac4b429efb75164341233955484af.
|
|
No functional change, just refactoring.
Follow-up for 6d9ef22acdeac4b429efb75164341233955484af.
|
|
This also adds basic comment about the return code.
Follow-up for 6d9ef22acdeac4b429efb75164341233955484af.
|
|
Follow-up for dcc359010c0a0d8366ade913bad72acb98f4f0ef.
|
|
Follow-up for a632d8dd9f6cd5cf8e43862f0ea896cc571b1cab.
|
|
Follow-up for d7a6bb9891ecc38a1bedef9689d00671bb0001ff.
|
|
|
|
|
|
|
|
Wired and 2.4G dongle connectivity is covered by general trackball rule,
but with Bluetooth connectivity Kensington SlimBlade Pro uses the name
"SlimBlade Pro" which doesn't contain "[Tt]rack[Bb]all". We need to
process it specially.
Signed-off-by: Celeste Liu <CoelacanthusHex@gmail.com>
|
|
We're not actually populating a filesystem here, we're preparing
to populate a filesystem, so update the log messages accordingly.
|
|
packages, and should be removed on package removal
(This excludes any dirs that contain resources placed there by the user)
(I also didn't bother marking resources belonging to components that are
really not optional for us)
|
|
Let's make the risk of accidental misuse, and mark lines that shall be
covered by --purge with an explicit new flag "$".
See: #33349
|
|
|
|
These are inspired by the existing commands that return the path to the
boot or ESP partitions. However, these new commands show the path to the
boot loader (systemd-boot) or UKI/stub (systemd-stub) that was used on
the current boot. This information is derived from EFI variables.
|
