| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | |
| | | |
ConditionNull= is the only condition where parameter==NULL is allowed,
and we'd print ConditionNull=(null) or ConditionNull=!(null).
|
| | |
| | |
| | |
| | |
| | | |
We didn't have a straightforward way to parse and evaluate those strings.
Prompted by #12881.
|
| | |
| | |
| | |
| | |
| | |
| | | |
In this mode we are not supposed to "interact with the environment", so loading
all units and printing warnings about syntax errors and /var/run usage seems
inappropriate.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Originally the description of conditions was brief, so it was acceptable
to put this part at the end. But now we have a myriad conditions, and
this crucial bit of information is easy to miss.
|
| | |
| | |
| | |
| | |
| | | |
No point in using u->id first, and doing assert(u) later.
-std=c89 strikes again.
|
|\ \ \
| | | |
| | | | |
systemd-sleep: use resume_offset value if set
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If hibernation is requested but /sys/power/resume and
/sys/power/resume_offset are not configured correctly, systemd-sleep
attempts to calculate swapfile offset using fstat and fiemap.
Btrfs returns virtual device number for stat and a virtual offset
for fiemap which results in incorrect offset calculations. In the
case where offset would be calculated and the user is using Btrfs,
log a debug message and fail to write device and offset values.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Use hibernation configuration as defined in
/sys/power/resume and /sys/power/resume_offset
if present before inspecting /proc/swaps and
attempting to calculate swapfile offset
|
|\ \ \ \
| | | | |
| | | | | |
cryptsetup: comment: crypt_setup → crypt_format
|
| | | | | |
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
s/and and/and/
s/explicity/explicitly/
s/that that/that/
s/the the/the/
s/is is/it is/
s/overriden/overridden/
|
|\ \ \ \
| |/ / /
|/| | | |
conf-parse: fix continuation handling
|
| | | | |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
Before this commit, empty lines cannot break continuation.
The bug was introduced by 9adbfeb38ac101d6f73a033bb120d63513ffb240.
Closes #12883.
|
|\ \ \
| |/ /
|/| | |
test: fix argument type of test_format_bytes_one()
|
| | |
| | |
| | |
| | | |
Closes #12891.
|
|/ / |
|
| |
| |
| |
| | |
apply_numa_policy()
|
|/
|
|
| |
Follow-up for 44e891bbf6908e494856fcf3011e88a70a12e087.
|
|
|
|
| |
Fixes: #12498
|
|
|
|
|
| |
Apart from making the code a little bit more clean, it should allow us
to write a fuzzer around the config-parsing functions in the future
|
| |
|
|\
| |
| | |
DynamicUser=1 → = 0 migration follow-up
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Incorporates some suggestions from:
https://github.com/systemd/systemd/pull/12868#discussion_r296738370
https://github.com/systemd/systemd/commit/cd69e88ba3a692618048117b26fc9ea339aa1845#commitcomment-34060775
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
| |
Remove the retired flag -d from Example 4. "Boot a minimal Arch Linux
distribution in a container". It has been retired here:
https://git.archlinux.org/arch-install-scripts.git/commit/pacstrap.in?id=0af6884aca68dcb7eed0b85fbc2960903df3d968
|
|\
| |
| | |
DynamicUser=1 state directory back migration
|
| |
| |
| |
| | |
Fixes: #12131
|
| |
| |
| |
| | |
(also line break again)
|
| |
| |
| |
| |
| |
| |
| | |
Takes a single /sys/fs/bpf/pinned_prog string as argument, but may be
specified multiple times. An empty assignment resets all previous filters.
Closes https://github.com/systemd/systemd/issues/10227
|
|\ \
| | |
| | | |
ethtool: make UBSan quiet and add missing link modes
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
tree-wide: further path_join() and path_joina() cleanups
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
| |/|
| | |
| | |
| | | |
When the first argument is '/' and the second argument is not absolute,
the return value was not prefixed with '/'. This fixes the issue.
|
|\ \ \
| |_|/
|/| | |
Various printing/logging fixes
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I have an .efi image with embedded newlinews. Now I don't even remember if it
was created for testing or by accident, but it doesn't really matter. We should
display such files correctly.
(This isn't a problem with normal BLS entries, because input is split into lines
so newlines are consumed.)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Those messages were quite confusing. In particular "adding address" suggests
that we are assiging a new address to an interface, but in fact we're just
reacting to a notification about an addition. So let's call that "remembering"
and "forgetting". It's not fully gramatically correct, but I think it's much
clearer than "adding"/"removing" in this context.
And "received address without address" is too cryptic, let's say "address
message" to distinguish the message from its content.
Also, make failure to format address non-fatal, and print more details in
various places.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For some reason, systemd-logind is trying to handle idle action in one of my containers:
Jun 07 10:28:08 rawhide systemd-logind[42]: System idle. Taking action.
Jun 07 10:28:08 rawhide systemd-logind[42]: Requested operation not supported, ignoring.
But we didn't log what exactly was being done. Let's put the name of the action in messages.
|
| | |
| | |
| | |
| | |
| | |
| | | |
All callers pass either a fixed action, or HANDLE_IGNORE is explicitly filtered
out. Let's remove this case here, because we cannot properly log what opreation
we are ignoring.
|