IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
Otherwise, if getopt() and friends are used before parse_argv(), then
the GNU extensions may be ignored.
This should not change any behavior at least now, as we usually use
getopt_long() only once per invocation. But in the next commit,
getopt_long() will be used for other arrays, hence this change will
become necessary.
(cherry picked from commit ef9c12b157a50d63e8a8eb710c013d16c2cea319)
(cherry picked from commit edfca36727c54a3dc1b77a25db436db25a63beee)
It's a bit nicer if we only write the sysctl core_pattern once the
coredump socket is established, since it's the backend for the handler.
Given the systemd-coredump.socket basically has no dependencies that run
before it this should not really make things slower or so, it just
removes the tiny window where core pattern is in effect that wants to
connect to the backend socket but cannot.
The status quo isn't terrible, and not too different in effect: either
way, until the socket unit is up we won't process coredumps. It's mostly
what kind of behaviour you get then: an error due to /bin/false being
invoked, or an error because systemd-coredump can't connect to its
socket. After this patch we'll exclusively see the former.
(cherry picked from commit 62c72c60b5e6c0712a45b1feccc6cc18151efa9c)
(cherry picked from commit 9943f2af3d46ae730443065aa781bbe04ee524ed)
The test log is in the state directory, and we want to keep it around
when a test fails.
Follow-up for: 256a835f1c6c646a55039659aa2db186fbeb5c5d
(cherry picked from commit 49e8342965649503a537beacb77dd0fafc71debe)
(cherry picked from commit dbb1b9c2c8419490b48a3a0aeb69bacbda232043)
SC2015: Note that A && B || C is not if-then-else. C may run when A is true.
(cherry picked from commit a5979f0bd50234ff9cad47f160d121628e0e3bbe)
(cherry picked from commit 18afac6e9086fd92835b0695ac1981149ef6ed32)
If people grep the output, it probably shouldn't be ellipsized.
(cherry picked from commit f735076c548abe9878e98c2da044458dd0e684f3)
(cherry picked from commit ff7040b19370d3572c4c84123103234e98e09c1f)
Also reduce the scope of variables.
(cherry picked from commit bc1f1eba776434f84f082bf4935b736c94dbb0f1)
(cherry picked from commit 00977a8e74e8fafd0f81356ca1f608766af00047)
Otherwise, directory with zero access mode cannot be removed.
(cherry picked from commit 808c8b25eece33c503430151641f5f77676af38c)
(cherry picked from commit 201830df218b08bb06e1ecbf43bc5987e77e0235)
No functional change hopefully, just for safety.
(cherry picked from commit da19c07198167946d35be9fdf908bb683da49cfe)
(cherry picked from commit d91f7eb0fb5839d6fc52ec74aca7c3aa44e3b5db)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
Otherwise, several error logs may not be shown.
(cherry picked from commit a723521fd26d40ce90357e4e9b8131f1e1656ab5)
(cherry picked from commit ce06e000b8b7d993670cdd2f827c92c7fef4c93e)
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)
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)
`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)
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)
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)
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)
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)
