1
1
mirror of https://github.com/systemd/systemd-stable.git synced 2025-03-13 12:58:20 +03:00

61088 Commits

Author SHA1 Message Date
Mike Yuan
f3678358a4 core/main: also check the argument terminator
For future-proof reasons, in case we will add
another option that starts with --deserialize.

Addresses 4f44d2c4f7 (r107285603)

(cherry picked from commit 09567df7db75824f1b8bf0b5cc721febda03cb56)
(cherry picked from commit ed18c2ab79e8b94182d5dcf31d58457763f3e3e1)
v252.9
2023-04-04 11:55:22 +01:00
Mike Yuan
b1ce97cffb core: do early setup check for arguments with '=' too
Follow-up for d2ebd50d7f9740dcf30e84efc75610af173967d2

We now modify our cmdline to use '=' for all arguments,
but didn't change early setup check to work with that.
So every daemon-reexec does a full setup, thus breaking
running user sessions.

Fixes #27106

(cherry picked from commit 4f44d2c4f76922a4f48dd4473e6abaca40d7e555)
(cherry picked from commit 4f4e0bab0d66ca6501432854aa3d3fcb53887796)
2023-04-03 11:40:16 +01:00
Дамјан Георгиевски
eae1851b12 add a github workflow action to make a release from tags
make a github release for every tag that starts with `v*`,
and a pre-release if the tag contains "-rc".

on the 'systemd/systemd' repo, the "Release" will be draft, so that the
release manager can fill up the notes manually.

on 'systemd/systemd-stable' the release will be created immediately.

info about the action used:
https://github.com/softprops/action-gh-release

(cherry picked from commit 86c20937c29da637878a1282444b057bc1a519fb)
(cherry picked from commit a3f2884ef29dee2ace12afe74b9d8d539237a10a)
2023-04-03 11:40:16 +01:00
Luca Boccassi
250729fff2 test: install 'script' for TEST-26-SYSTEMCTL
Needed by 744ea4536f6a535313a8c7f3ad2f069b51a3a933
2023-03-31 01:12:58 +01:00
Zbigniew Jędrzejewski-Szmek
51e72a8a4e hwdb: update to 201423d80144d60b48144c6283d669b63a80aabe
git restore -s origin/main hwdb.d/ test/hwdb.d test/hwdb-test.sh

(cherry picked from commit 4c80732d232733759b7e4ca2ff13e23db6b565cb)
v252.8
2023-03-30 20:50:51 +02:00
Zbigniew Jędrzejewski-Szmek
48e0395535 shared/exec-util: null_or_empty_path() does not return boolean
We shouldn't report that the file is empty if the stating fails. Let's do the
same as in other places, and just ignore the error and let the subsequent
operation fail.

(cherry picked from commit 7d0c47dad0d4282c3924a654a8fe18fc5d7766f8)
(cherry picked from commit bfc03cae41ae051c9eedcb48f66b3266346719aa)
2023-03-30 19:21:34 +02:00
Lennart Poettering
34e83c24a7 man: correct/tweak text about unit name syntax
Unit names can be 255 characters long, not 256.

We first say "name prefix" and then continue with "unit prefix".
Confusing. Couldn't figure out which term is better hence settled on
"unit name prefix".

(cherry picked from commit 75f7e5e54704e643aa9b50ce03ed02a49e75333f)
(cherry picked from commit a2ef3c97bd38d189a4b2cb5c6248f01558c7c9d8)
2023-03-30 19:21:34 +02:00
David Tardon
760059bd64 journal-vacuum: count size of all journal files
Currently, active journal files are excluded, which means that vacuuming
may not remove anything even if *MaxUse= has been exceeded.

(cherry picked from commit 9ea46af4f2368b41d57705bac09774778126507f)
(cherry picked from commit e4c7553874e86ada52545e26aafb318ca91e9545)
2023-03-30 19:21:34 +02:00
Frantisek Sumsal
7eca133c1d test: add a couple of tests for userdbctl
(cherry picked from commit 93fe228bb16afdb7c450af26b4d2e5771016a833)
(cherry picked from commit e1ddc48ff934209db70d4de0f3fa6fcf5225b359)
2023-03-30 19:21:34 +02:00
Frantisek Sumsal
73afda3f6d userdbctl: flush stdout before running the chain command
Otherwise it's quite difficult to capture the entire output:

$ userdbctl ssh-authorized-keys dropinuser --chain /bin/echo hello
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIA//dxI2xLg4MgxIKKZv1nqwTEIlE/fdakii2Fb75pG+ foo@bar.tld
ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBMlaqG2rTMje5CQnfjXJKmoSpEVJ2gWtx4jBvsQbmee2XbU/Qdq5+SRisssR9zVuxgg5NA5fv08MgjwJQMm+csc= hello@world.tld
hello
$ userdbctl ssh-authorized-keys dropinuser --chain /bin/echo hello | tee
hello

(cherry picked from commit 5b09499cacd3c1c95ab240d041e28cc954a5975d)
(cherry picked from commit 0e7745249b1c576f89fb97ee76c3bf4c83d8f299)
2023-03-30 19:21:34 +02:00
Frantisek Sumsal
ebcd284358 docs: s/authorized_key/authorized_keys/
(cherry picked from commit 13bf3216101af82d36e24e5a95f450f166f5030b)
(cherry picked from commit e17d4351a7b6126e8f42b3eaa8ac28d444d35620)
2023-03-30 19:21:34 +02:00
Frantisek Sumsal
50a9e9a5b0 man: s/io.systemd.Dropin/io.systemd.DropIn/
(cherry picked from commit 8f572d0d82f2f8bb3995faa569da5af1ef7a427d)
(cherry picked from commit 5d2588b5940b03c72371ec2af84dc79ed5703e85)
2023-03-30 19:21:34 +02:00
Frantisek Sumsal
a13bd7deb5 userdbctl: don't show legend when dumping JSON with services
(cherry picked from commit eedd1da9f992f9b9d38e298207428500b745156b)
(cherry picked from commit 1185e7f9d3730c6bf3ab0b537b9e811e12aa8ed0)
2023-03-30 19:21:34 +02:00
Lennart Poettering
f76e47b810 analyze: don't claim "@known" was an unlisted syscall
It's a sycall group of our own definition, and the output is erroneous
to claim otherwise. Let's hide it.

This adds syscall_set_add() which is nicely symmetric to the existing
syscall_set_remove().

Follow-up for: 6d6a08547c03f96dc798cda1ef4a8d3013d292d5

(cherry picked from commit 950c0ed38935198a67a57c645e499555eaf006eb)
(cherry picked from commit 7822ae021b795f55f84499d00763e112229ac6b4)
2023-03-30 19:21:31 +02:00
Lennart Poettering
4b0ae9d418 seccomp-util: add some newer syscalls to existing groups
These three new syscalls are mostly just new flavours or extensions of
existing syscalls, hence add them to the same groups.

(cherry picked from commit 76e86b8dd8cca9f9fee120289945b29e1dbbe215)
(cherry picked from commit 54f97c0ae5ca3e8560fabcfacc1687715e64477e)
2023-03-30 19:12:37 +02:00
Zbigniew Jędrzejewski-Szmek
c71bd9c535 xdg-autostart-generator: do not warn about unknown fields
My user manager says:
systemd-xdg-autostart-generator[2933]: /home/zbyszek/.config/autostart/org.gnome.Terminal.desktop:256: Unknown key name 'Actions' in section 'Desktop Entry', ignoring.
systemd-xdg-autostart-generator[2933]: /home/zbyszek/.config/autostart/org.gnome.Terminal.desktop:258: Unknown section 'Desktop Action new-window'. Ignoring.
systemd-xdg-autostart-generator[2933]: /home/zbyszek/.config/autostart/org.gnome.Terminal.desktop:343: Unknown section 'Desktop Action preferences'. Ignoring.
systemd-xdg-autostart-generator[2933]: /home/zbyszek/.config/autostart/org.telegram.desktop.desktop:12: Unknown key name 'Actions' in section 'Desktop Entry', ignoring.
systemd-xdg-autostart-generator[2933]: /home/zbyszek/.config/autostart/org.telegram.desktop.desktop:13: Unknown key name 'SingleMainWindow' in section 'Desktop Entry', ignoring.
systemd-xdg-autostart-generator[2933]: /home/zbyszek/.config/autostart/org.telegram.desktop.desktop:19: Unknown section 'Desktop Action Quit'. Ignoring.

This is not useful. Those are externally-provided files, and they are likely to
have entries which we know nothing about.

(cherry picked from commit b5a70eeecdb593f8498c0bc163d5a12297cfb55d)
(cherry picked from commit 90ba721560b67e329fff4f2c4e59f5c578d8f440)
2023-03-30 19:12:32 +02:00
наб
cd3d4ab738 find-esp: don't silently error bootctl install if presumed XBOOTLDR part is stx_dev_major=0 but not btrfs
btrfs_get_block_device_fd() returns -ENOTTY if fstatfs().f_type !=
BTRFS_SUPER_MAGIC

btrfs_get_block_device_fd() is run by verify_fsroot_dir() by
verify_xbootldr() by find_xbootldr_and_warn() if
statx($presumed-XBOOTLDR).stx_dev_major == 0 ("maybe a btrfs device")

Every bootctl verb_install() runs find_xbootldr_and_warn(), by default
with /boot

If your /boot .stx_dev_major=0 but /not/ btrfs, bootctl install/update
quietly exits 1 with no note so as to what exactly failed (debug also
empty, and the strace isn't exactly clear since no syscall actually
failed)

This is the case on ZFS and the Debian filesystem layout: /boot/efi is
the ESP, and everything else under / is ZFS:
  $ sudo env SYSTEMD_LOG_LEVEL=debug bootctl update
  Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy
  Found container virtualization none.
  File system "/boot" is not a FAT EFI System Partition (ESP) file system.
  Using EFI System Partition at /boot/efi.
  Checking whether /boot/efi/EFI/systemd/ contains any files…
  $ echo $?
  1
and funnier still:
  $ sudo bootctl update --graceful
  $ echo $?
  1

Which is great, and also breaks postinst, which runs precisely the
latter, with no feedback at all

By checking for -ENOTTY we accept that the path being investigated
"is not it" if it's on ZFS (and any other filesystem that returns
.stx_dev_major == 0 but isn't btrfs)

(cherry picked from commit ed89819f8fd7bfe99cd652082076e85e1417e4e9)
(cherry picked from commit f6388f561cad25f440c2637ce3f1399ed8ed9b7f)
2023-03-30 19:12:22 +02:00
Daan De Meyer
dc92016bd7 core: Settle log target if we're going to be closing all fds
Whenever we're going to close all file descriptors, we tend to close
the log and set it into open when needed mode. When this is done with
the logging target set to LOG_TARGET_AUTO, we run into issues because
for every logging call, we'll check if stderr is connected to the
journal to determine where to send the logging message. This check
obviously stops working when we close stderr, so we settle the log
target before we do that so that we keep using the same logging
target even after stderr is closed.

(cherry picked from commit a3b00f91bb985fa10bc33db5c7883e33dbdf83d0)
(cherry picked from commit 22c47d24a447112bbf8022a79d9c3940a2f04316)
2023-03-30 19:12:10 +02:00
Yu Watanabe
b5f7c05204 activate: use log_set_open_when_needed()
Otherwise, several error logs may not be shown.

(cherry picked from commit a723521fd26d40ce90357e4e9b8131f1e1656ab5)
(cherry picked from commit ce06e000b8b7d993670cdd2f827c92c7fef4c93e)
2023-03-30 19:12:05 +02:00
Kevin P. Fleming
769d65988d bootctl: 'graceful' should ignore EFI variable failures
Suppress errors when creating/writing EFI variables during 'bootctl update' if
'--graceful' mode is active (as the documentation indicates).

Closes #26773.

(cherry picked from commit 06d104d58ffa23c958b9b2a2809c61fb25e6f762)
(cherry picked from commit b041337a7a5219398cb304e6cb31456327a7e371)
2023-03-30 19:11:51 +02:00
Thomas Blume
d9c2ae019a udev-rules: fix nvme symlink creation on namespace changes
The nvme by-id symlink changes to the latest namespace when a new namespace gets
added, for example by connecting multiple NVMe/TCP host controllers via nvme
connect-all.
That is incorrect for persistent device links.
The persistent symbolic device link should continue to point to the same NVMe
namespace throughout the lifetime of the current boot.
Therefore the namespace id needs to be added to the link name.

(cherry picked from commit c5ba7a2a4dd19a2d31b8a9d52d3c4bdde78387f0)
(cherry picked from commit 059ca4fe8fc4740adc9690689f03de491b8d0e61)
2023-03-30 19:08:20 +02:00
Antonio Alvarez Feijoo
357a3f1d2b man/network-generator: replace dracut.kernel reference with dracut.cmdline
`dracut.kernel.7` is just a symlink to `dracut.cmdline.7`, so the web reference
points to a non-existent URL
(https://man7.org/linux/man-pages/man7/dracut.kernel.7.html).

(cherry picked from commit 9baeb58fcdcd3b8893fc485bb33726820ce46e94)
(cherry picked from commit 2a8c1168b11f7144d98fa126bc9a06a2bc92383d)
2023-03-30 19:08:14 +02:00
Antonio Alvarez Feijoo
5e5aacd16f gpt-auto-generator: fix typo
(cherry picked from commit dd23292c080f6e8b972c63b025ad3997972bc9e4)
(cherry picked from commit ad2d77b8994a336643114627e327fc5426f1d335)
2023-03-30 19:08:08 +02:00
David Tardon
8bf89dddac systemctl: always print circular deps. at the end
Before:
a.target
○ └─b.target
    ├─...
●   └─paths.target

After:
a.target
○ └─b.target
●   ├─paths.target
    └─...

(cherry picked from commit bb7c4a93ea1167b1294f86307d712d45655e9632)
(cherry picked from commit c86983c58a8ca57b15ef4d401262b64d4d27a254)
2023-03-30 19:07:56 +02:00
David Tardon
0b058ee2bf systemctl: fix formatting of circular dep.
Before:
a.target
○ └─b.target
    └─...
●   └─paths.target

After:
a.target
○ └─b.target
    ├─...
●   └─paths.target

(cherry picked from commit 5a4711e4895e3f7091e0e4da654412232484a5ec)
(cherry picked from commit 6903f28d8d8261b03fc30f279d401e22ad81cbd9)
2023-03-30 19:07:55 +02:00
David Tardon
571f9d5828 systemctl: fix indentation of circular deps
We're still at level `level` here.

Before:
b.target
○ ├─a.target
  │   └─...
● └─paths.target

After:
b.target
○ ├─a.target
  │ └─...
● └─paths.target

Fixes #26052.

(cherry picked from commit a9f2f486f3d1dd1cd2a58cd384b0e88970e2fda9)
(cherry picked from commit cee098e4e17dd9aefe9ce8866fbf4c9ebe21fb00)
2023-03-30 19:07:54 +02:00
Mike Yuan
e913b51c5b systemctl: list-dependencies: pass bool where appropriate
(cherry picked from commit 8e481bd29258274b4d92737d4b11636eabfffcb5)
2023-03-30 19:07:48 +02:00
Yu Watanabe
48abbdda56 tmpfiles: show file type in octal, instead of hex
(cherry picked from commit 056ff0b455ec54c9cadd119b09d0ec36efdee808)
(cherry picked from commit 7ca1a3a1d43488d254b515a59bf40a75b94bff8b)
2023-03-30 19:06:39 +02:00
Daan De Meyer
603d8402de units: Order user@.service after systemd-oomd.service
The user manager connects to oomd over varlink. Currently, during
shutdown, if oomd is stopped before any user manager, the user
manager will try to reconnect to the socket, leading to a warning
from pid 1 about a conflicting transaction.

Let's fix this by ordering user@.service after systemd-oomd.service,
so that user sessions are stopped before systemd-oomd is stopped,
which makes sure that the user sessions won't try to start oomd via
its socket after systemd-oomd is stopped.

(cherry picked from commit cafd2c0be404cb8879f91d15e05cc8b695b32629)
(cherry picked from commit c4848032f132e0cb82c7967e5434378c98111a8c)
2023-03-30 19:06:35 +02:00
Mike Yuan
9ced8895e1 sleep: fix default values unmatched with manual
(cherry picked from commit f05b4bb9a7a70092641f43486fc7a45c85fc9c63)
(cherry picked from commit fd963d1bc806f900fc8a3310f7110fdedac3958d)
2023-03-30 19:06:09 +02:00
Addison Snelling
8a711f1c26 man: fix misspelled executable name (#26858)
(cherry picked from commit 0c868e3fada33c7139112f0268c29307bdcd6ee7)
(cherry picked from commit 37f65e46d3a4ecb6cc1a48bd5ee72d8342609077)
2023-03-30 19:06:04 +02:00
Zbigniew Jędrzejewski-Szmek
df2ff69d16 man: document "Delegate=" a bit more
This case is a bit surprising, even if logical if one understands how the
parser works. Let's be more explicit.

Follow-up for 7b3693e4e4c9cae50fca65136278a62fae11327e.

(cherry picked from commit 449172f943acadc7fd1e2293a615c7cb0d87fcd6)
(cherry picked from commit 2ead535f0d0ceec9b3b9565ed056c3ccef0779af)
2023-03-30 19:05:40 +02:00
Daan De Meyer
974baa7ac0 mkfs-util: Always use "default" usage type for ext filesystems
If no usage type is explicitly specified, ext will choose one based
on the filesystem size. Let's override this and always use the
"default" usage type so that we can create filesystems that are
initially small but might grow later without opting in to the "small"
usage type.

(cherry picked from commit 59c3c195f432243a1d4b2a7210e9699db83cb335)
(cherry picked from commit 1b51f6a8f0f7fc891b2d5885190fdaffd82ccea2)
2023-03-30 19:05:31 +02:00
Daan De Meyer
56c4a34fa0 man: Fix user generator output paths
These are all under $XDG_RUNTIME_DIR/systemd instead of directly
under $XDG_RUNTIME_DIR.

(cherry picked from commit 80c7d4b8fa9f8283af7f0213739e3463c68a30f6)
(cherry picked from commit 16183e66f63f2023f77a3088c8a8ca7f3de9db59)
2023-03-30 19:02:40 +02:00
Morten Linderud
b1b266b79f man: Fix pcrphase.service manvolnum from 1 to 8
(cherry picked from commit 9e60dc0daffdb3c8b137c9ec529d7942e1c52124)
(cherry picked from commit 67ba5637c0ae6f1c5be218b94f66f8b16b5ef632)
2023-03-30 19:02:20 +02:00
Morten Linderud
f58091416c src: Fixup copy-paste error for terminal_urlify_man
Signed-off-by: Morten Linderud <morten@linderud.pw>
(cherry picked from commit 6dadf31d6123a9127ee6ceccbcc272d53ec5f8fa)
(cherry picked from commit e7e6043ccf253f57a9e3455eb3d58112892c70fb)
2023-03-30 19:01:56 +02:00
Will Fancher
ad061062eb mount: Include After=local-fs-pre.target by default in initrd
Although it may be true that /sysroot and its children don't belong in
local-fs.target, that doesn't mean they shouldn't come after
local-fs-pre.target. For instance, systemd-hibernate-resume@.service needs to
come before /sysroot and its children, but currently that only happens
coincidentally because of the ordering between systemd-fsck@.service and
local-fs-pre.target. As a result, mount units can be mistakenly started
simultaneously with systemd-hibernate-resume@.service, which can cause
corruption and data loss in the worst of cases.

(cherry picked from commit 6e017b19a804639101fc87b4b78c02f7639c6d0c)
(cherry picked from commit c7280b7c1f2bfeb4054c17eecd8a70f022115c32)
2023-03-30 19:01:51 +02:00
Frantisek Sumsal
35f3b83cd6 test: fall back to /sys/fs/cgroup/systemd if necessary
Necessary for some CI setups where we boot an nspawn container on a host
with older systemd with legacy hierarchy, so systemd mounts its stuff
under /sys/fs/cgroup/systemd.

(cherry picked from commit 715b4c26dc9f447a8d7b8cab33c243e15386ce2c)
(cherry picked from commit ff746117083e7418e378e46868aad601db57d920)
2023-03-30 19:01:47 +02:00
Frantisek Sumsal
b67fad80e0 test: force mkfs.btrfs to overwrite any existing file systems
mkfs.btrfs (unlike mkfs.ext4) checks if the target already contains
a file system and refuses to continue if so. This causes spurious fails
in case the random garbage on the temporary device matches a valid FS
header:

[   19.723806] testsuite-64.sh[355]: + udevadm lock --device=/dev/mapper/encbtrfs0 --device=/dev/mapper/encbtrfs1 --device=/dev/mapper/encbtrfs2 --device=/dev/mapper/encbtrfs3 mkfs.btrfs -M -d raid1 -m raid1 -L btrfs_mencdisk -U deadbeef-dead-dead-beef-000000000003 /dev/mapper/encbtrfs0 /dev/mapper/encbtrfs1 /dev/mapper/encbtrfs2 /dev/mapper/encbtrfs3
[   19.918934] testsuite-64.sh[2494]: ERROR: /dev/mapper/encbtrfs0 appears to contain an existing filesystem (hfsplus)
[   19.920490] testsuite-64.sh[2494]: ERROR: use the -f option to force overwrite of /dev/mapper/encbtrfs0

Let's force mkfs.btrfs to overwrite the file system in such case.

(cherry picked from commit b3ba7d6274aff864a80dc9b1ff7d88ad376da451)
(cherry picked from commit 12c3b1980b47a87139c3f4406161df69e7515873)
2023-03-30 19:01:40 +02:00
Zbigniew Jędrzejewski-Szmek
f4764ea126 man: adjust description of CPUAccounting=
For any user on a semi-recent kernel, effectively this setting is pointless.
We should deprecate it once not needed anymore for the v1 hierarchy. For
now, adjust the description.

(cherry picked from commit 695e39dd632801871b4e96b39bc8e7511083a34e)
(cherry picked from commit 4b12a1cf9249a2e59c2824958dfa6d56222c5d68)
2023-03-30 19:01:08 +02:00
Zbigniew Jędrzejewski-Szmek
52e2479bd6 man: add a note about session autogrouping
When cpu controller is disabled, thing would often still behave as if
it was. And since the cpu controller can be enabled "magically" e.g. by
starting user@1000, add a note for users to be careful. Autogrouping
is described well in the man page, incl. how to enable or disable it,
so it should be enough to refer to that.

(cherry picked from commit dca031d2290311d8670d34fd758397644796e114)
(cherry picked from commit 6bef1f00852aaf7e0e599f510c84e97e3a27eed9)
2023-03-30 19:01:07 +02:00
Zbigniew Jędrzejewski-Szmek
97ecc1c6b3 man: tweak details in descriptions of pids and cpu configuration
For CPUWeight=: there is an important distinction between our default of
[not set], and the kernel default of "100". Let's not say that our default
is "100" because then 'systemctl show' output is hard to explain.

For task accounting, it's the kernel that does the accounting, not systemd.

(cherry picked from commit 396d298d6b0c50a3ab3242392de43dd50df6d45f)
(cherry picked from commit 2a31faf6255e06b757274d20cf98fdd8eae64fc6)
2023-03-30 19:01:06 +02:00
Zbigniew Jędrzejewski-Szmek
7646f29a84 man: describe how cgroup controllers are turned on
For a user, information which cgroup controllers are enabled based on
the unit configuration is rather important. Not only because it determines
what resource control is peformed by the kernel, but also because controllers
have a non-negligible cost, especially for deep nesting, and users may want
to *not* have controllers enabled.

Our documentation did its best to avoid the topic so far. This was partially
caused by the support for cgroup v1, which meant that any discussion of
controllers had to be conditional and messy. But v1 is deprecated on its way
out, so it should be fine to just describe what happens with v2.

The text is extended with a discussion of how controllers are enabled and
disabled, and an example, and for various settings that enable controllers
the relevant controller is now mentioned.

(cherry picked from commit 253d0d591bdca605c9a775e22407f9ae80003234)
(cherry picked from commit da8c0e0978c0fc91a70dbd5139208274cd8d9c0d)
2023-03-30 19:00:55 +02:00
Zbigniew Jędrzejewski-Szmek
1114a7a522 man: explain route-only domains a bit more
The details discussion of how search and route-only domains work is in
systemd-resolved.service(8). But users are more likely to look at
resolved.conf(5), because that's where Domains= is described. So let's add a
reference to the other man page there, and also strengthen the text a bit. In
particular, in systemd-resolved.service(8) we say "route-only", which makes
the distinction with search domains clearer. Let's use the same in the other
man page too.

This is based on feedback from Lukáš Nykrýn that the man page is not clear
enough.

(cherry picked from commit 87291a26f5262c47bdb3493d15534c18f25870e6)
(cherry picked from commit c7afeee1e6b42d2c68074dc0b89ace502a16315b)
2023-03-30 19:00:22 +02:00
Yu Watanabe
0e29ec09dd man: mention systemd-growfs-root.service
(cherry picked from commit 61ccf030aef82e335941260b82381d0056b475c7)
(cherry picked from commit b8b20dc261751598b8b4ddfcd9c2e3244b938571)
2023-03-30 19:00:03 +02:00
Yu Watanabe
720cb50229 man: mention systemd-fsck-usr.service
(cherry picked from commit 5e9750533586efa3d480ac2bc4cf8549993bc3f1)
(cherry picked from commit 20f71ba98f9e55796693cdbd5d0416c372a7056c)
2023-03-30 19:00:02 +02:00
Jan Engelhardt
08cffef584 doc: correct wrong use "'s" contractions
(cherry picked from commit 18fe76eba59dc494597b07e0114899b69f92cc12)
(cherry picked from commit c181761f9a600066217da2c590d63555ec6c3eba)
2023-03-30 18:59:55 +02:00
Jan Engelhardt
7f44993923 doc: replace wrong á preposition by à
(cherry picked from commit 3ff1721c219479ec51479970f1d81a3aa17e9b50)
(cherry picked from commit 21266ac59df21c2fd3bdc1838ed0d9e152019f32)
2023-03-30 18:59:30 +02:00
Yu Watanabe
3e270826ce test: add header build tests for newer C and C++ standards
(cherry picked from commit a6d46fe64b61c62dc5c0dadbad65134075b29303)
(cherry picked from commit efbe08c27cb3881f154142a1797cb32034ad4748)
2023-03-30 18:59:24 +02:00
Cristian Rodríguez
dd9c50c6cb Include <threads.h> if possible to get thread_local definition
IN C23, thread_local is a reserved keyword and we shall therefore
do nothing to redefine it. glibc has it defined for older standard
version with the right conditions.

v2 by Yu Watanabe:
Move the definition to missing_threads.h like the way we define e.g.
missing syscalls or missing definitions, and include it by the users.

Co-authored-by: Yu Watanabe <watanabe.yu+github@gmail.com>
(cherry picked from commit 5545f336fd09148e8d9aa7f83ed19384deaf7a64)
(cherry picked from commit 25b5c24e59b63abe081c31e3d9a3dd392c2fdbae)
2023-03-30 18:59:18 +02:00