| Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Fixes #6712. The newline is later reversed, naturally.
|
|
Related to issues #9107 and #9498 and PRs #9149 and #9157.
|
|
Otherwise, they will end up in /dev/null.
|
|
|
|
Follow-up for a6bb550458. Suggested by @ignatenkobrain.
$ rpmbuild --eval %_environmentdir
/usr/lib/environment.d
$ rpmbuild --eval %_environmnentdir
warning: Use %_environmentdir instead
/usr/lib/environment.d
|
|
|
|
One mention of --user was missing the surrounding <option> tag, making
the table look inconsistent (though the inconsistency is less obvious
after the reordering in 709f4c472c, since the four specifiers mentioning
the --user option are no longer immediately adjacent).
|
|
- Reset systemd-networkd.service before each test run, to avoid running
into restart limits.
- Our networkd-test-router.service unit needs to run as root and thus
can't use `User=`; but networkd still insists on the
`systemd-network` system user to exist, so create it.
|
|
|
|
There are some modern programming languages use userspace context switches
to implement coroutine features. PowerPC (32-bit) needs syscall "swapcontext" to get
contexts or switch between contexts, which is special.
Adding this rule should fix #9485.
|
|
|
|
Follow-up for cc7d50a5714bc810af51b0c55be12b4f55acc089.
|
|
|
|
Follow-up for 0c697941389b7379c4471bc0a067ede02814bc57.
|
|
For #9320.
|
|
This is already included in .dir-locals, so we don't need it
in the files themselves.
|
|
Required and seems to work in 238.133
|
|
to make sure that there's enough room for unstripped binaries.
|
|
The D-Bus library supplies a va_list variant of
`sd_bus_message_append()` called `sd_bus_message_appendv()`,
but failed to provide a va_list variant of its opposite,
`sd_bus_message_read()`. This commit publicizes a previously static
function as `sd_bus_message_readv()`.
|
|
|
|
Follow-up for f43580f17d9977ea330deacc8931982e41a49abf.
|
|
ENABLE_GSHADOW is defined to be 0 or 1. So #if should be used instead of #ifdef.
|
|
This commit adds accel mount matrix for DEXP Ursus 10XW and Z110i tablets. In current state (*svn*DEXP*:*pn*DEXPOEM*) it will apply to many (if not almost all) BayTrail-based tablets with Windows by DEXP (with same DMI strings) but this expected to cause no (or very little) harm as this devices is mostly very similar with slight difference.
However, if correction of this quirk becomes necessary in the future, this DMI strings could be used to distinguish 10XW and Z110i from other tablets by DEXP.
DEXP Ursus 10XW: dmi:bvnTechvisionHASHVersion96AC8868:bvr5.6.5:bd12/26/2014:svnDEXP:pnDEXPOEM:pvr1.0:rvnDEXP:rnDEXPOEM:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
DEXP Ursus Z110i Apollo: dmi:bvnTechvisionHASHVersion1DE28747:bvr5.6.5:bd03/14/2015:svnDEXP:pnDEXPOEM:pvr1.0:rvnDEXP:rnDEXPOEM:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
|
|
|
|
Originally, request_name_handler_may_reload_dbus() was written for
timesyncd. But now it is also called by networkd or resolved.
|
|
|
|
|
|
|
|
Closes #9396.
|
|
|
|
Suggested by LGTM: https://lgtm.com/rules/1506024027114/
|
|
Closes #9450.
|
|
This fixes the following warning:
```
meson.build:1140: WARNING: Trying to compare values of different types (DependencyHolder, list) using !=.
The result of this is undefined and will become a hard error in a future Meson release.
```
Follow-up for f02582f69fe1e7663a87ba80bd4f90d5d23ee75f(#9410).
|
|
This makes OBJECT_PATH_FOREACH_PREFIX consistent with PATH_FOREACH_PREFIX
and also fixes 7 alerts reported by LGTM at
https://lgtm.com/projects/g/systemd/systemd/snapshot/ac0a08700344a5690803df8dd80e8bb5013184a5/files/src/libsystemd/sd-bus/bus-objects.c?sort=name&dir=ASC&mode=heatmap&showExcluded=true#V1383
|
|
|
|
nspawn as it is now is a generally useful tool, hence let's drop the
comments about it being useful for debug and so on only.
The new wording just makes the first sentence of the main page also the
summary.
|
|
Use PRIu64 constant to get the format right on LP-64 architectures,
cast to (uint64_t) to solve incompatibility of __u64.
This was missed in ad4bc3352285f467f4ffa03c3171b19fa0a8758d, so fix it
with this follow up.
|
|
Fixes: 96f64eb5741b157f26a9089816fdd992e959792e
Closes: https://github.com/systemd/systemd/issues/9444
|
|
For loopback volumes, the generated unit needs to depend on
systemd-tmpfiles-setup-dev.service to ensure that loopback
support is loaded.
Fixes #9308
|
|
Fixes #9442.
|
|
This also fixes minor memleak introduced in
654457e560c5723b90b419f7651b87040aade07e.
|
|
Also use compat_main() when called as `resolvconf`, since the interface
is closer to that of `systemd-resolve`.
Use a heap allocated string to set arg_ifname, since a stack allocated
one would be lost after the function returns. (This last one broke the
case where an interface name was suffixed with a dot, such as in
`resolvconf -a tap0.dhcp`.)
Tested:
$ build/resolvconf -a nonexistent.abc </etc/resolv.conf
Unknown interface 'nonexistent': No such device
Fixes #9423.
|
|
Discovered by LGTM.
|
|
Discovered by LGTM.
|
|
Suggested by LGTM.
|
|
|
|
Use PRIu64 and PRIu32 constants to also get the format right on LP-64
architectures.
For the 64-bit fields, we need a cast to (uint64_t), since __u64 is
defined as a `long long unsigned` and PRIu64 expects a `long unsigned`.
In practice, both are the same, so the cast should be OK.
|
|
Now that @yuwata has fixed a lot of alerts, the badge looks
much better than before, so let's show it :-)
|
|
This should be removed after systemd 240 is released.
Signed-off-by: Neal Gompa <ngompa13@gmail.com>
|
