Age | Commit message (Collapse) | Author |
|
journal: reduce minimum journal file size to 512 KiB
|
|
test: Fix typo in TEST-03-JOBS/test-jobs.sh
|
|
core: remove unused variable
|
|
unused since 7b2313f5
|
|
Fix typo s/enqueueing/enqueuing/
Signed-off-by: Jesus Ornelas Aguayo <jesus.ornelas.aguayo@intel.com>
|
|
networkd: fix option name in log message
|
|
test-execute: don't use /usr/bin/uname. use sh and PATH
|
|
|
|
For low end embedded systems 4 MiB for each journal file is a lot of
memory. Journald will use at least 512 KiB even if JOURNAL_FILE_SIZE_MIN is
set to less than that so just use 512 KiB.
|
|
|
|
core: parse socket port to extract_first_word
|
|
detect-virt: one fix and arm/aarch64 dmi detection
|
|
test-functions: fix dbus-1 installation
|
|
The basic setup for the well-known system and session buses is
now done in read-only files in ${datadir} (normally /usr/share).
See the NEWS entry for 1.9.18 for details.
http://cgit.freedesktop.org/dbus/dbus/tree/NEWS
|
|
Some guests (ARM, AArch64, x86-RHEL) have 'KVM' in the product name.
Look for that first in order to more precisely report "kvm" when
detecting a QEMU/KVM guest. Without this patch we report "qemu",
even if KVM acceleration is in use on ARM/AArch64 guests.
I've only tested a backported version of this and the previous
patch on an AArch64 guest (which worked). Of course it would be
nice to get regression testing on all guest types that depend on
dmi done.
|
|
ARM/AArch64 guests now have SMBIOS tables populated (when boot
with a late enough QEMU and a late enough AAVMF is used as the
bootloader). Furthermore, when booting ARM/AArch64 guests with
ACPI, the DT detection obviously no longer works, so we need
dmi detection.
|
|
afaict, this will fix a regression caused by commit 75f86906c5.
Where we used to report "kvm" before that patch, without this patch,
we would only report "qemu". The reason is because cpuid detection
must come before dmi detection. Also, both can safely come before
other xen heuristics. Untested.
|
|
bash-completion: add minimal support fpr 'set-property' command
|
|
systemctl: update documentation for --plain option
|
|
core: fix typo
|
|
|
|
core: small fixes to parse_namespace
|
|
- Existing documentation did not mention that --plain omits the bullets and works on list-units and list-machines.
|
|
sd-daemon: fix potential LISTEN_FDS overflow in sd_listen_fds()
|
|
'set-property' was missing from the list of known command.
Also a list of unit names will be proposed as next argument.
However no support on property names is provided since it would
require a hard coded list of them.
|
|
* don't hide ENOMEM
* log r instead of 0
|
|
|
|
|
|
restore journald watchdog
|
|
|
|
We already filter out 0, and as -1 is usually special (meaning infinity,
as in USEC_INFINITY) we should better not accept it either. Better safe
than sorry...
|
|
After all, this is not some compiler or C magic, but something very
specific to how systemd works, hence let's move it into def.h, and out
of macro.h
|
|
|
|
(V2) networkd: bridge convert to jiffies
|
|
|
|
|
|
sd-pppoe: drop
|
|
It is really unclear if we want to / have the resources to support this fully, so drop it
for now. It can easily be brought back if a killer usecase emerges.
Note that this code was never hooked up, so this does not remove any features.
|
|
networkd: (de)serialize more state and support expiring routes
|
|
Fixed link to chattr man page
|
|
|
|
util-linux 2.27.1's configure.ac still claims to be 2.27.0, which breaks our
version check. Lower it back to 2.27.0 until util-linux gets a fixed tarball.
See #1754
|
|
debug-generator: respect kernel parameters for default unit setting
|
|
|
|
|
|
|
|
core: drop check for /etc/mtab
|
|
man: Drop "internally," which is misleading
|
|
A grab bag of stuff
|
|
The existing text misleads readers into thinking how the notify socket protocol is "internals" and that they can only use the functions. However, the socket is part of the Interface Stability Promise. So, we should drop "internally" from the description so the man page both indicates both how the functions work and how one would talk to the socket directly.
|