| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\
| |
| | |
test-load-fragment: fix memleak
|
| | |
|
| |
| |
| |
| | |
Fixes a leak reported at https://github.com/systemd/systemd/pull/26115#issuecomment-1398026085.
|
| |
| |
| |
| | |
Follow-up for da20baaeccbcca78350bf64bdc069dec685c95bc.
|
|\ \
| | |
| | | |
timesync: some tweaks to saved timestamp file handling
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Let's make sure the timestamp file's mtime is guaranteed to change for
each boot, so that it is a useful indicator of time. Or in other words
this gurantees that systemd-timesyncd.service acts as a new kind of
milestone: that time definitely progressed on this boot even the machine
died abnormally imediately after.
|
| | |
| | |
| | |
| | | |
Let's log more.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
disk timestamp
It's useful being able to easily detect if a disk-based clock bump was
done, let's make it a structure message, the same way as acquiring an
NTP fix already is.
Also, set the clock to 1 µs further than the timestamp from the disk,
after all we know that that timestamp was current when it was written,
hence it can't be the right one right now anymore.
|
| | | |
|
| | | |
|
| | | |
|
| |/
|/|
| |
| | |
character buffers to NUL terminated C strings
|
| | |
|
| |
| |
| |
| | |
SD_ID128_TO_STRING()
|
|\ \
| |/
|/| |
bootctl --help fixes
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
--help text
grub (at least on fedora) nowadays implements the boot loader spec, but
not the boot loader interface. Hence let's split out the commands
specific to each in two groups in the --help text. This way the first
group just covers boot lodaer spec stuff (i.e. stuff on disk in the
ESP/XBOOTLDR partition). And the other covers talking to the boot loader
via EFI var.
|
| |
| |
| |
| |
| | |
for some reason the descriptions of the switches and the commands
weren't aligned, one space off. Fix that.
|
| |
| |
| |
| | |
Let's call them kernel *images*, not just *kernels*.
|
| |
| |
| |
| | |
We never do that, don't do so here either.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
If output fields are specified, let's store this in a Set right-away,
instead of converting between strv and Set again and again for each
line.
This is not only faster, but also simpler and shorter.
|
| | |
|
|\ \
| |/
|/| |
hostnamectl: show firmware date as date only, with now time
|
| |
| |
| |
| |
| | |
The source (usually DMI/SMBIOS) only has 24h granularity, hence don't
show time as well, it's useless.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
|
| |
Removing debugging related sections is apparently not enough to truely
strip a (PE) binary.
Better late than never. It gets rid of this pesky warning from sbsign:
warning: data remaining[174080 vs 193173]: gaps between PE/COFF sections?
|
|\
| |
| | |
sd-login: add sd_pidfd_* APIs
|
| |
| |
| |
| |
| |
| | |
Same as the sd_pid_* counterparts, but take a pid file descriptor instead of
a pid, so that the callers can be sure that the returned values are really
about the process they asked for, and not about a recycled PID.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
These combine strndup() + strspn()/strcspn() into one.
There are a bunch of strndupa() calls that could use similar treatment
(or should be converted to strdup[c]spn(), but this commit doesn't
bother with that.
|
|\ \
| | |
| | | |
basic: Add log context
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit adds support for attaching extra metadata to log
messages written to the journal via log.h. We keep track of a
thread local log context in log.c onto which we can push extra
metadata fields that should be logged. Once a field is no longer
relevant, it can be popped again from the log context.
On top of this, we then add macros to allow pushing extra fields
onto the log context.
LOG_CONTEXT_PUSH() will push the provided field onto the log context
and pop the last field from the log context when the current block
ends. LOG_CONTEXT_PUSH_STRV() will do the same but for all fields in
the given strv.
Using the macros is as simple as putting them anywhere inside a block
to add a field to all following log messages logged from inside that
block.
void myfunction(...) {
...
LOG_CONTEXT_PUSH("MYMETADATA=abc");
// Every journal message logged will now have the MYMETADATA=abc
// field included.
}
For convenience, there's also LOG_CONTEXT_PUSHF() to allow constructing
the field to be logged using printf() syntax.
log_context_new()/log_context_free() can be used to attach a log context
to an async operation by storing it in the associated userdata struct.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Let's use statement expressions to return values instead of passing
in return arguments to the LIST macros.
|
| | |
| | |
| | |
| | |
| | |
| | | |
We want to include stdio-util.h in log.h in a future commit. To avoid
circular includes, we need to drop the memory-util.h include from
stdio-util.h
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This allows passing pre-allocated buffers via compound initializers
to snprint_ok(). If snprintf_ok() is a macro, the compound initializer
block will be scoped to the macro block, if snprint_ok() is a function,
the compound initializer block will be scoped to the block from which
snprintf_ok() is called.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
There is a later model version of the Chuwi Hi10X that has significantly changed components compared to the existing hwdb one. Differentiator (on Chuwi forums, in thesofproject, etc.) is the N4120 rather than the N4100 processor.
The svn and pn seem to be identical, my Chuwi Hi10X matches with the old model except for the changed KIOX000A* iio sensor.
With the added ACCEL_MOUNT_MATRIX, my device works on gnome and has the correct (right-up) output in monitor-sensors.
|