| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Add "move" action as per src/libsystemd/sd-device/device-private.c
|
| |\
| |
| | |
network: do not touch kernel-created multicast route
|
| | | |
|
| | |
| |
| |
| | |
Fixes #6088.
|
| | |
| |
| |
| |
| | |
The HHKB Pro JP has no leds whatsoever, record that. The sysfs
file "capabilities/led" says "1f".
|
| |\ \
| | |
| | | |
more v243 news preparation
|
| | | | |
|
| | | |
| | |
| | |
| | | |
It's an internal function we define, noone else should bother.
|
| |/ / |
|
| |\ \
| |/
|/| |
ntp-units.d support
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Users might end up with more than one of those service enabled, through
admin mistake, or broken installation scriptlets, or whatever. On my machine,
I had both chronyd and timesyncd happilly running at the same time. If
more than one is enabled, it's better to have just one running. Adding
Conflicts will make the issue more visible in logs too.
|
| | |
| |
| |
| |
| |
| |
| | |
Priority is 80. At least in Fedora, chrony uses 50, and ntpd 60.
timesyncd has lower priority, because if people install those other packages,
it's most likely on purpose. timesyncd is always installed and provides
less functionality.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We removed support for foreign services (and ntp-units.d/) in b72ddf0f4.
Support for foreign services was added back in 5d280742, but through an
environment variable.
The problem with the env var approach is that it only works as a mechanism
to select one item, and doesn't work nicely as a mechinism to create a list
of items through drop-ins (because the env var can be easily overridden, but not
extended). Having a list of "ntp providers" is important to be able to reliably disable
all of them when that is requested.
Another problem is that nobody ever bothered to care about our new "standard".
ntp-units.d/ is a nice simple format that works and is already supported by
chrony and ntpd and timedatex. If we were to introduce and ask people to follow
a new standard, there should be some good reason for this. The idea with env
vars has lower functionality, requires systemd-specific syntax. We should just
re-adopt the format that we originally introduced and that seems to work for
everyone, and more on to more interesting problems.
|
| |\ \
| | |
| | | |
Revert of #12378 ("VT kbd reset check")
|
| | | |
| | |
| | |
| | |
| | | |
Let's make clearer that toggle_utf8_sysfs() is about sysfs, and
toggle_utf8_vc() about VC access
|
| | | |
| | |
| | |
| | | |
This reverts commit bb5ac84d79ac3aef606a4a9eeaafef94a1f199be.
|
| | | |
| | |
| | |
| | | |
This reverts commit 13a43c73d8cbac4b65472de04bb88ea1bacdeb89.
|
| | | | |
|
| |\ \ \
| |_|/
|/| | |
pstore: refuse to run if arguments are specified
|
| | | |
| | |
| | |
| | |
| | | |
Don't try to use <<<. It seems to not work properly with old bash
versions or something.
|
| | | |
| | |
| | |
| | | |
(This is why the --help chech passed.)
|
| |\ \ \
| | | |
| | | | |
pstore: several minor follow-ups
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Previously, the return value of the last read_full_file() is returned.
This makes the error in read_full_file() is always ignored.
|
| | | | | |
|
| | |/ /
| | |
| | |
| | | |
Found by @mattiasb.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In recent systemd-nspawn we wouldn't parse init args like systemd.log-level=debug.
This is because we wouldn't even look at /proc/1/cmdline.
$ systemd-nspawn -n cat /proc/1/stat
1 (cat) R 0 1 1 34816 ....
^^^^^
34816 is 136:0 a.k.a. /dev/pts/0.
|
| |/ /
| |
| |
| | |
https://bugzilla.redhat.com/show_bug.cgi?id=1655316
|
| |\ \
| | |
| | | |
Preparatory work for the unit loading rework
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
So far we put such functinos in install.[ch], but that is tied too closely
to enable/disable. Let's start moving things to a place with a better name.
|
| | | |
| | |
| | |
| | |
| | | |
The caller looks for directories and is called "..._find_dirs()". Here, there
is no "finding" going on, so I found the old name confusing.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
No functional change.
|
| | | |
| | |
| | |
| | | |
Another case where "open code" is easier to read than the helper.
|
| | | |
| | |
| | |
| | | |
No functional change, but it's nicer to the reader.
|
| | | |
| | |
| | |
| | | |
It looks like we made a mistake. The list is just empty, that's all.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This file was testing a mix of functions from src/core/load-fragment.c and some
from src/shared/install.c. Let's name it more appropriately. I want to add
tests for the new unit-file.c too.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
comment
Effectively this does two more tests also for ordered hashmaps.
This setup is a bit confusing, let's add a comment.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
So far, we'd use hashmap_free_free to free both keys and values along with
the hashmap. I think it's better to make this more encapsulated: in this variant
the way contents are freed can be decided when the hashmap is created, and
users of the hashmap can always use hashmap_free.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Also make string_strv_hashmap_put return 0 only if the entry already existed.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This could already be done by calling unit_name_is_*(), but if we don't know
if the argument is a valid unit name, it is more convenient to have a single
function which returns the type or possibly an error if the unit name is not
valid.
The values in the enum are sorted "by length". Not really important, but it
seems more natural to me.
|
| | | | |
|
