| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
A distro (Fedora in particular) may want to enable oomd in a unstable
branch for testing, even though the package as a whole is compiled in release
mode. Let's emit a warning but otherwise allow this.
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
D-Bus error reply
Closes #17556.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is useful for development where overwriting files out side
the configured prefix will affect the host as well as stateless
systems such as NixOS that don't let packages install to /etc but handle
configuration on their own.
Alternative to https://github.com/systemd/systemd/pull/17501
tested with:
$ mkdir inst build && cd build
$ meson \
-Dcreate-log-dirs=false \
-Dsysvrcnd-path=$(realpath ../inst)/etc/rc.d \
-Dsysvinit-path=$(realpath ../inst)/etc/init.d \
-Drootprefix=$(realpath ../inst) \
-Dinstall-sysconfdir=false \
--prefix=$(realpath ../inst) ..
$ ninja install
|
| | |
| |
| |
| | |
Follow-up for db9ecf050165fd1033c6f81485917e229c4be537.
|
| |\ \
| |/
|/| |
Various small cleanups
|
| | | |
|
| | |
| |
| |
| |
| | |
Inspired by coverity CID#1435984. I'm confused by the union definion every time I look at it...
Let's at least add a comment to help future readers.
|
| | |
| |
| |
| |
| |
| | |
... when called with a valid environment variable name. This means that
any time we call it with a fixed string, it is guaranteed to return 0.
(Also when the variable is not present in the environment block.)
|
| | | |
|
| | |
| |
| |
| |
| | |
With this change the pattern used for epoll_ctl() is the same in all calls in
this file. Consistency FTW!
|
| | |
| |
| |
| |
| | |
Neither source_child_pidfd_register() nor event_make_signal_data() look at
n_enabled_child_sources.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Coverity in CID#1435966 was complaining that s->enabled is not "restored" in
all cases. But the code was actually correct, since it should only be
"restored" in the error paths. But let's still make this prettier by not setting
the state before all operations that may fail are done.
We need to set .enabled for the prioq reshuffling operations, so move those down.
No functional change intended.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
":" is prettier, but meson 0.56+ doesn't like it:
src/systemd/meson.build:73: DEPRECATION: ":" is not allowed in test name "cc-sd-bus.h:c", it has been replaced with "_"
src/systemd/meson.build:73: DEPRECATION: ":" is not allowed in test name "cc-sd-bus.h:c-ansi", it has been replaced with "_"
...
Fixes #17568.
|
| |\ \
| | |
| | | |
Use app.slice by default in user manager (and define special user slices)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
With the grandparent change to move most units to app.slice,
those units would be ordered After=app.slice which doesn't make any sense.
Actually they appear earlier, before the manager is even started, and
conceputally it doesn't seem useful to put them under any slice.
|
| | | |
| | |
| | |
| | |
| | | |
The only visible change from this is that we show Extrinsic: yes/no
in dumps for swap units (this was already done for mount units).
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Add documentation for the special slice user slice units.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This changes the default from putting all units into the root slice to
placing them into the app slice in the user manager. The advantage is
that we get the right behaviour in most cases, and we'll need special
case handling in all other cases anyway.
Note that we have currently defined that applications *should* start
their unit names with app-, so we could also move only these by creating
a drop-in for app-.scope and app-.service.
However, that would not answer the question on how we should manage
session.slice. And we would end up placing anything that does not fit
the system (e.g. anything started by dbus-broker currently) into the
root slice.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This adds app.slice, session.slice and background.slice.
|
| | | |
| | |
| | |
| | |
| | | |
Explain why this is useful, but don't describe the implementation exactly,
since we're likely to want to change details in the future.
|
| |\ \ \
| | | |
| | | | |
V247 rc2 prep
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
The content was already there, but it wasn't listed in the header
metadata. Fix that.
|
| | | | | |
|
| | | | | |
|
| |/ / / |
|
| |\ \ \
| | | |
| | | | |
timer: add new feature FixedRandomDelay=
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
FixedRandomDelay=yes will use
`siphash24(sd_id128_get_machine() || MANAGER_IS_SYSTEM(m) || getuid() || u->id)`,
where || is concatenation, instead of a random number to choose a value between
0 and RandomizedDelaySec= as the timer delay.
This essentially sets up a fixed, but seemingly random, offset for each timer
iteration rather than having a random offset recalculated each time it fires.
Closes #10355
Co-author: Anita Zhang <the.anitazha@gmail.com>
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
This PR adds logitech G403 to the hwdb.
Settings were obtained with 'sudo mouse-dpi-tool /dev/input/event3' and 'ratbagctl hollering-marmot info'.
|
| |\ \ \ \
| | | | |
| | | | | |
ethtool: make ethtool_get_driver() return -ENODATA if driver is an empty string.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
driver name is empty
Inspired by #17532.
|
| | | | | | |
|
| | |_|_|/
|/| | |
| | | |
| | | | |
Fixes #17502.
|
| |\ \ \ \
| | | | |
| | | | | |
udev: make algorithm that selects highest priority devlink less susceptible to race conditions
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
to race conditions
Previously it was very likely, when multiple contenders for the symlink
appear in parallel, that algorithm would select wrong symlink (i.e. one
with lower-priority).
Now the algorithm is much more defensive and when we detect change in
set of contenders for the symlink we reevaluate the selection. Same
happens when new symlink replaces already existing symlink that points
to different device node.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Note that st_mtime member of struct stat is defined as follows,
#define st_mtime st_mtim.tv_sec
Hence we omitted checking nanosecond part of the timestamp (struct
timespec) and possibly would miss modifications that happened within the
same second.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Since 'test/udev-test.pl: count "good" results', we know how many
checks succeeded. Add an "expected good" count to make that number
more meaningful.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
umount emits an error message "no mount point specified" if the
tmpfs isn't mounted yet, which is the normal case.
Suppress that by redirecting stderr.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Script for generating LOTS of SCSI disk and partition devices in
the fake sysfs we use for udev testing.
This script is supposed to be run after sys-script.py. It uses
code from sys-script.py as template to generate additional SCSI disk data
structures. Together with the "generator" code in udev-test.pl
added in the previous patch, it allows to run udev tests with almost
arbitrarily many devices, and thus to do performance scaling tests.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Manually listing all devices in the test definition becomes cumbersome with
lots of devices. Add a function that scans on all block devices in
the test sysfs and generates a list of devices to test.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
for easier reproduction of sporadic test failures.
|
