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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
When processing list of units (either provided manually or as a
wildcard), let's skip units for which we don't have an on-disk
counterpart, but note the -ENOENT error code and propagate it back to
the user.
Fixes: #14082
(cherry picked from commit a25457f5b7689265bd2235c4da218896e7c5c1d0)
(cherry picked from commit 8b1bd17469892de5838509c6794a8a38432c01b0)
Files specified with EnvironmentFile are read from PID1 mount namespace, before
any file system operations like RootImage or BindPaths are in effect.
(cherry picked from commit 412a6c646ced41ac9b12c4a4f97e34c0350e1040)
(cherry picked from commit b2f342f92b5447b68c5c61a1d078c62f26ddfd20)
The example shows the output of critical-chain, which means
that the title is wrong.
(cherry picked from commit be78e0f07b2379f51e6530269be953c0b520c447)
(cherry picked from commit 945f3a231f6fd0b5fa1dd3e11b9223b4c1dff37a)
We were checking the uid, whereas we should have checked the gid
(cherry picked from commit 98cd752a285c0fba84b8d98f3ba255ed4d11c881)
(cherry picked from commit 2c8ae283b0eebdbc92f4832fca8e46a00be5b246)
We fucked up errno vs. r two times, let's correct that.
While we are at it, let's handle the error first, like we usually do,
and the clean case without indentation.
(cherry picked from commit 88287615e631d2023ff337a08b6ff45b1cfa58ee)
(cherry picked from commit 6b48479f458257ff1769c88d46208ba56209b067)
This reverts commit 07125d24eedb71693b3bf2b1f0730cd01aaac2dd.
In contrast to what is claimed in #13396 dbus-broker apparently does
care for the service file to be around, and otherwise will claim
"Service Not Activatable" in the time between systemd starting up the
broker and connecting to it, which the stub service file is supposed to
make go away.
Reverting this makes the integration test suite pass again on host with
dbus-broker (i.e. current Fedora desktop).
Tested with dbus-broker-21-6.fc31.x86_64.
(cherry picked from commit b895fa08e6809ab54e20888f7d01ae848272e981)
(cherry picked from commit faba5b2ba8c9cc07e431ab02b4917fc782cb89b9)
I think this makes it easier to see the difference between local and remote
mounts.
Make the graph a bit narrower while at it.
(cherry picked from commit f71502c49fd9fce6328f9364f600578383551dce)
(cherry picked from commit 1c80a8ced006f92dc83e7ec36edd0005d4e54a76)
Instead of requiring both RootImage and RootDirectory directives, give badness
points if neither is present. Fixes conversion in d737b451f.
(cherry picked from commit d909b40fda52d6822a0f7201f9c17818df2bd091)
(cherry picked from commit 0130a03179f687c050247ee7e4367f0f4987a7f2)
Otherwise, systemd-udev-trigger|settle.service that ran in the initrd may
ramain active, and never re-run again from the system root.
This is observed by forexample examining ESP with udevadm info, which in the
initrd has all the ID_* variables, and none of them in fully booted system.
(cherry picked from commit f27bb6abd3b825034e0dde631ae3047128d2162d)
(cherry picked from commit 946cdba156dd385ffa86131664d808f36aaa24b7)
The code existed in machinectl to use stdin/stdout if the path for
import/export tar/raw was empty or dash (-) but a check to
`fd_verify_regular` in importd prevented it from working.
Update the check instead to explicitly check for regular file or
pipe/fifo.
Fixes#14346
(cherry picked from commit 1209ef94bd09bdc67a7b51f084910a5982f2f010)
(cherry picked from commit cfced59a4bd88e7d77ecf9ed40a22ec215356a83)
The code was using timeout=0 as the default option string. This option string
was ultimately passed to generator_write_timeouts(), which only looks for
comment=systemd.device-timeout= or x-systemd.device-timeout=, i.e. the whole
call path was bogus. Let's rework this: generator_write_timeouts() now writes
any timeouts if configured by the user. create_disk() writes out it's own
timeout, but with lower priority. Since the code path that was calling
timeout=0 was not effective, the only change is that we stop overwriting the
timeout if explicitly configured by the user.
In both code paths, ignore failure to write.
(cherry picked from commit 7cecc563163f539c497ecdf5ab00729fcd8c97c1)
(cherry picked from commit dc56b94e13089bbabcf75d962a11fec26b829093)
Ideally, we would want to report this over back over dbus. But that is pretty hard,
because the unitfile parsing logic doesn't provide any feedback.
systemd-analyze verify also doesn't notice the issue, because it doesn't look
at the [Install] section at all. Let's print a message in the logs at least.
(cherry picked from commit e51712963b817995781534975470f1b54171702b)
(cherry picked from commit 0757ad565573ad96ad8c3b4957ecf850fcc97042)
Real syscall numbers start at 0. The fake seccomp values seem to be
strictly less than 0.
Fixes: 4df8fe8415eaf4abd5b93c3447452547c6ea9e5f
(cherry picked from commit fb4b0465abbd96e6d342e5606c61c919c99a82ff)
A follow-up for 59b657296a2fe104f112b91bbf9301724067cc81, adding the
same conditioning for all cases of our __NR_xyz use.
Fixes: #14031
(cherry picked from commit 4df8fe8415eaf4abd5b93c3447452547c6ea9e5f)
The kernel resets the ipv6 mtu after NETDEV_UP or NETDEV_CHANGEMTU event,
so we must reset the ipv6 mtu to our configured value after we detect
IFF_UP flag set or after we set the device mtu.
Fixes: #13914.
(cherry picked from commit d236718c167af46bbf4460fc6b82db8396bd43a5)
(cherry picked from commit 639dc9f4bfd2c09535bee079ae9bc7006b520a66)
Don't reset the conflict counter when trying a new pseudo random
address, so that after trying 10 addresses the londer timeout is used in
accordance with the RFC
Fixes#14299.
(cherry picked from commit e92b60b20f21111a0c28135c1b5c78fc851a4f15)
(cherry picked from commit 1ba2e7a73000fedbf4b9a9af3a3e893f5f26eb9d)
This fixes a double "or" in the text of `systemctl --help`.
(cherry picked from commit ab4fae0c8c3fae4d3d67bf6e1176bbda1dfa208e)
(cherry picked from commit bcf0aa02bf68cfd8b55ecaa5221a246a63a9646f)
This switches detect_container() to path_is_read_only_rw("/sys"), as if
systemd-udevd.service is conditionalized with that way.
This also updates the log message.
(cherry picked from commit bf331d87171b7750d1c72ab0b140a240c0cf32c3)
(cherry picked from commit 96d7083c5499b264ecebd6a30a92e0e8fda14cd5)
If /sys is read only filesystem, e.g., nspawn is running in container,
then usually udev is not running. In such a case, let's assume that
the interface is already initialized. Also, this makes nspawn refuse
to use the network interface which is under renaming.
Fixes#14223.
(cherry picked from commit 26208d5b9674079dcf2c9d301f09a7c7b23bfdc3)
(cherry picked from commit e874419902892d4bc272475b14446fe8385b0e8b)
This is needed when systemd is compiled without systemd-tmpfiles
(cherry picked from commit a652f050a78616efb9e75c5b49c925400c64dded)
(cherry picked from commit 29c9144655de34494c424a36b6b42e2776db817e)
Negative priorities are useful for swap targets which should be only used as
last resort.
(cherry picked from commit 7477451b691d288dad67b4c8ce9e519e9b75770d)
(cherry picked from commit c08429ae339089a04be21c65d2ecd0dd784102ba)
That is what is linked from systemd.swap(5) and also what the systemd.generator produces.
(cherry picked from commit 88eb0519722f285e5264a909f16ddf2648190681)
We dropped documentation from sd_journal_open_container() long ago
(since the call is obsolete), hence drop the reference to machined. But
add one in for journald instead.
(cherry picked from commit d18df32d8229aff0bed41e9fe2a7a61598d70c89)
This partially reverts a07a7324adf504381e9374d1f1a5db6edaa46435.
We have two pieces of information: the value and a boolean.
config_parse_timeout_abort() added in the reverted commit would write
the boolean to the usec_t value, making a mess.
The code is reworked to have just one implementation and two wrappers
which pass two pointers.
(cherry picked from commit a61d68748afef4814760774eb0458a46d4ea9922)
We can break if KEYCTL_READ return value is equal to our buffer size.
From keyctl(2):
On a successful return, the return value is always the total size of
the payload data. To determine whether the buffer was of sufficient
size, check to see that the return value is less than or equal to the
value supplied in arg4.
(cherry picked from commit 6da498c28f2598bea4d651756485f57d54e379f4)
cryptsetup introduced optional locking scheme that should serialize
unlocking keyslots which use memory hard key derivation
function (argon2). Using the serialization should prevent OOM situation
in early boot while unlocking encrypted volumes.
(cherry picked from commit 408c81f62454684dfbff1c95ce3210d06f256e58)
If udevd receives an exit signal, it releases its reference on the udev
monitor in manager_exit(). If at this time a worker is hanging, and if
the event timeout for this worker expires before udevd exits, udevd
crashes in on_sigchld()->udev_monitor_send_device(), because the monitor
has already been freed.
Fix this by testing the validity of manager->monitor in on_sigchld().
(cherry picked from commit 030f4571670537c76355c5d923468c9a61aa77e9)
In those two pages, we need to include individual entries with xi:include to
merge the list less-variables.xml with the other entries, which is obviously
error prone. All variables are supported in both tools so add them.
(cherry picked from commit 3d58bfc01c9283eded77736990ea09b0ee4f6e23)
I see we log this during every boot, even though it is a routine expected event:
Nov 12 14:50:01 krowka systemd[1]: systemd-journald.service: Service has no hold-off time (RestartSec=0), scheduling restart.
(and for other services too). Let's downgrade this to debug level.
https://bugzilla.redhat.com/show_bug.cgi?id=1614871
(cherry picked from commit 868f7d36cc26552cc7377a6a81913fa8803bc3bb)
