| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Another fix in style of bd169c2be0fbdaf6eb2ea7951e650d5e5983fbf6.
Let's also avoid strjoina() in a loop (i.e. stack allocation). While in
this specific caseone could get away with it (since we'd immediately
afterwards leave the loop) it's still ugly, and every static checker
would be totally within its rights to complain.
Also, let's simplify things by not relying on argc, since it's redundant
anyway, and it's nicer to just treat things as NULL terminated strv
array.
Fixes: #12180
|
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
systemd-journal-remote always wrote the boot-id of the device it was running on
to the header of its journal files. When the source had a different boot-id
(because it was generated on a different boot, or a different device), the
boot-ids in the file were inconsistent. The _BOOT_ID field was that of the
source, but the journal file header and each entry object header were that of
the device systemd-journal-remote ran on. This breaks journalctl --list-boots
on any of these files.
Set the boot-id in the header to be that of the source. This also fixes the
entry object headers.
|
| | |
| | |
| | |
| | | |
Fixes #12145.
|
|\ \ \
| |/ /
|/| | |
.timer OnClockChange= and OnTimezoneChange= settings
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Fixes: #6228
|
| | |
| | |
| | |
| | |
| | | |
The value is directly initialized from cmdline args, hence let's name it
so, following our usual naming style.
|
|/ / |
|
| |
| |
| |
| |
| | |
Manual page systemd.generators refers to /etc/systemd/{system,user}-generators,
but the paths do not exist, so let's install them.
|
|\ \
| | |
| | | |
add ConditionCPUs= + ConditionMemory=
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
We have all the building blocks in place already, let's add this.
Fixes: #8990
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Let's add a new helper for determining how many CPUs are configured for
us
|
| | |
| | |
| | |
| | |
| | |
| | | |
Let's split out the operator parsing and the final verdict
determination. That way we can reuse this logic for other purposes later
on.
|
|\ \ \
| | | |
| | | | |
three minor tweaks to the man pages
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
let's be clearer about the overriding concept for OnCalendar= settings.
Prompted by this thread:
https://lists.freedesktop.org/archives/systemd-devel/2019-March/042351.html
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Let's avoid confusion whether the root is at the top or of the bottom of
the directory tree. Moreover we use "innermost" further down for the
same concept, so let's stick to the same terminology here.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In particular, let's not use gotos that jump up, i.e. are loops. gotos
that jump down for the purpose of clean-up are cool, but using them for
loops is evil.
No change in behaviour, just some refactoring.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
wait-online: add --any option
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When this option is specified, wait-online exits with success even
when several interfaces are in configuring state.
Closes #9714.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
yuwata/network-fix-and-extend-foo-over-udp-support
network: fix and extend Foo over UDP
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Otherwise, multiple FOU tunnels cannot be created correctly.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Previously the setting is ignored and always FOU_ENCAP_GUE is sent.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
It's not easy to implement such a combined operation race-freely since
dropping a subvolume will drop all its contents, including any
non-directories.
Hence, let's just not support this combination for now. Which isn't much
of a loss, since we never combine these flags anyway.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
We keep track of it, but never exposed it. Let's fix that.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Let's shorten the code a bit by using a single function for similar
cases.
No change in behaviour, just some refactoring and shortening.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
two tweaks for timer expression parsing
|
| | | | | | | |
|
| | |_|/ / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
logic
No change of behaviour. Let's just not parse the lvalue all the time
with timer_base_from_string() if we can already pass it in parsed.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes: #12165
|
| |/ / / /
|/| | | | |
|