| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| | |
Fix memory protection default setting
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, an empty assignment of Memory{Low,Min}= directives would be
interpretted as setting it to global default, i.e. zero. However, if we
set a runtime protection value on a unit that inherits parent's
DefaultMemory{Low,Min}=, it is not possible to revert it back to the
state where the DefaultMemory{Low,Min}= is propagated from parent
slice(s).
This patch changes the semantics of the empty assignments to explicitly
nullify any value set by the user previously. Since DBus API uses
uint64_t where 0 is a valid configuration, the patch modifies DBus API
by exploiting the variant type of property value to pass the NULL value.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When MemoryLow= or MemoryMin= is set, it is interpretted as setting the
values to infinity. This is inconsistent with the default initialization
to 0.
It'd be nice to interpret the empty assignment as fallback to
DefaultMemory* of parent slice, however, current DBus API cannot convey
such a NULL value, so stick to simply interpretting that as hard-wired
default.
|
| | |
| |
| |
| | |
Corrected reference to non-existent unit.
|
| |\ \
| | |
| | | |
dissect: single-filesystem verity images with external hashdevice
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
dm-verity support in dissect-image at the moment is restricted to GPT
volumes.
If the image a single-filesystem type without a partition table (eg: squashfs)
and a roothash/verity file are passed, set the verity flag and mark as
read-only.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Single filesystem images are mounted from the /dev/block/X:Y symlink
rather than /dev/loopZ, so we need to wait for udev to create it or
mounting will be racy and occasionally fail.
|
| | | |
| | |
| | |
| | |
| | | |
'udevadm settle --timeout=XY' will return 1 in case the timeout was
reached and the event queue was not empty.
The manpage should mention it.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
On some CIs, it may takes more than 40 seconds.
Hopefully fixes #16105.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Arch recently upgraded systemd to 245.6. Shortly afterwards, users began
reporting[0] that systemd detected an ordering cycle, and they were
unable to log in. The reason they were unable to log in was because of
ordering cycle resolution:
[...]
systemd[1]: sysinit.target: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with sysinit.target/start
systemd[1]: sysinit.target: Job systemd-update-done.service/start deleted to break ordering cycle starting with sysinit.target/start
systemd[1]: sysinit.target: Job systemd-journal-catalog-update.service/start deleted to break ordering cycle starting with sysinit.target/start
systemd[1]: sysinit.target: Job local-fs.target/start deleted to break ordering cycle starting with sysinit.target/start
systemd[1]: sysinit.target: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with sysinit.target/start
[...]
Whether the resolution did the right thing here or not is a longer-term
discussion, but in the interim we should at least make this distinction
between automount dependencies and mount dependencies clearer in the
documentation, so that users and distribution maintainers know what's
acceptable. In this case Arch actually backed out b3d7aef5 entirely and
released a new version due to the confusion.
Also see https://github.com/systemd/systemd-stable/issues/69.
0: https://bugs.archlinux.org/task/66908
|
| | | |
| | |
| | | |
Boolean type in varlink is named bool, not boolean.
|
| |\ \ \
| | | |
| | | | |
Freezer test flakes
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
return too early
Actually, it is the same kind of problem as in d910f4c . Basically, we
need to return 1 on success code path in slice_freezer_action().
Otherwise we dispatch DBus return message too soon.
Fixes: #16050
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
freeze/thaw
Fixes: #16050
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Assigning seats to specific USB ports lets the devices plugged into them
inherit the port's seat assignment.
|
| |\ \ \ \
| | | | |
| | | | | |
9p is a network filesystem
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Not every filesystem that is not a network filesystem and also not an API VFS
filesystem has a corresponding block device.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
The function returns true if the specified filesystem requires a block device.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The usual behaviour when a timeout expires is to terminate/kill the
service. This is what user usually want in production systems. To debug
services that fail to start/stop (especially sporadic failures) it
might be necessary to trigger the watchdog machinery and write core
dumps, though. Likewise, it is usually just a waste of time to
gracefully stop a stuck service. Instead it might save time to go
directly into kill mode.
This commit adds two new options to services: TimeoutStartFailureMode=
and TimeoutStopFailureMode=. Both take the same values and tweak the
behavior of systemd when a start/stop timeout expires:
* 'terminate': is the default behaviour as it has always been,
* 'abort': triggers the watchdog machinery and will send SIGABRT
(unless WatchdogSignal was changed) and
* 'kill' will directly send SIGKILL.
To handle the stop failure mode in stop-post state too a new
final-watchdog state needs to be introduced.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Bash completion for homectl and help improvement for kernel-install
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The difference between verbs that take one user and multiple users is not
handled. I don't know how to do this.
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Update gdb script to match current sources and other hashmap improvements
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
"internal" is a lot of characters. Let's take a leaf out of the Python's book
and simply use _ to mean private. Much less verbose, but the meaning is just as
clear, or even more.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Now: set, 0x7f19be8f7c20 <string_hash_ops>, False, 1, 1, 4, unit_new, src/core/unit.c:96
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
mypy is occasionally useful for checking python scripts.
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Afaict, this code never worked, since even when this code was added in
2ea8c08306c7e33f8217a878cf990fc491c9432c, neither all_entry_sizes nor
all_direct_buckets were defined.
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This makes debugging hashmaps harder, because we can't query the size. Make
sure that table is always present.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This follows PEP 8 and matces other python code in systemd.
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
udev: optionally mark all block devices popping up read-only by default
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The suggested syntax is simply not valid and results in an error.
|
| | | | | | | | | |
|
| | | |_|_|_|/ /
| |/| | | | | |
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
networkctl: add support to display DHCPv4 client ID
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Tested on HP Spectre x360 Convertible 13-aw0xxx
|
| |\ \ \ \ \ \ \ \
| |_|/ / / / / /
|/| | | | | | | |
network: introduce IPv4AcceptLocal= setting
|
| | | | | | | | | |
|
| |/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
Closes #16090.
|
| |/ / / / / / |
|
