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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
systemd-boot selects the last valid entry by default, not the first.
Fixes: #15256
(cherry picked from commit e6190e2882e1d6772a9e586fcc65c91d406e52fb)
(cherry picked from commit c5883bc08877d8bad10110434037a3c21950a71a)
(cherry picked from commit f047b0706c01f99c1b781f44b7b4d95ecdb8abe2)
This documents the syntax
enable template@.service foo bar baz
that was introduced in #9901 to preset templated units.
(cherry picked from commit 1f667d8a7cff4355cd23ebebeb4d7179e3498eb8)
(cherry picked from commit d1d3f2aa1561a9a75ce58026ef0a6bd4c5b464ac)
(cherry picked from commit f4d5928122fe632b441145750a03d95fd8dd2cc6)
(cherry picked from commit 0b1b0a01ab22c088046634c46c496022e7e60673)
(cherry picked from commit 3c69813c69af90e75acf9a80047ecf5b075c138d)
(cherry picked from commit 148f7b147aaba46491cec23ec44e4e998a84900f)
(cherry picked from commit 1cee1c52833fb6e3829e510109404852a17e5bdd)
(cherry picked from commit ffccc15f725fe8d9d39a44978168cc483820d750)
(cherry picked from commit 1ea52d91c80b9012f4f76e660122e04ef3f86bc8)
A minor clarification in the manual page is made.
Signed-off-by: Antonio Russo <antonio.e.russo@gmail.com>
(cherry picked from commit 81248e7f3e83a24cbbc8d2a09a01abf55e81bcda)
(cherry picked from commit 82dd4caf014c97eb9d7ab9da2841f7866e91bd98)
The first section header in that example should probably be `[NetDev]` and not `[Xfrm]`.
(cherry picked from commit a15e1a5df0c943ec5414014e54719bd1259fd00a)
(cherry picked from commit a60459764d9d4a3a7a32332768d9dbfb9f311dfc)
'stored on disk' gives the impression that this option affects only
permanent storage, even though it affects everything the journal
records, regardless of the storage type.
Use 'stored in the journal' to avoid confusion.
(cherry picked from commit c97ae2b29036af29480ee506a072525917f5d41f)
(cherry picked from commit c001a285a3a2edfd344756e636f18f226fc291c4)
There are sometimes users who put unit files in a location that is inaccessible
when systemd starts although they are not found and thus not started because
the corresponding mount units have not activated yet.
There is already a warning for such issue in man 8 systemctl:
link PATH...
...<snip>...
The file system where
the linked unit files are located must be accessible
when systemd is started (e.g. anything underneath /home
or /var is not allowed, unless those directories are
located on the root file system).
However, it looks that it's difficult to find the warning because introductory
users typically doesn't know systemctl link.
Although there is a description in UNIT FILE LOAD PATH pointing to systemctl
link, symlink is now not explicitly mentioned there and thus users doesn't
easily get aware of they should read it.
To deal with this, let's describe "symlink" and "systemctl link" more
explicitly in UNIT FILE LOAD PATH.
(cherry picked from commit b63c88b6271804e4770a14d94c66210e0c8063d7)
(cherry picked from commit c22bf6b31a454e51c707dcd0e6993f09ea6758db)
We generate "v" in two different ways, and they got mixed up.
(cherry picked from commit a1686563ded4cb6967034a59a61a50534c952dad)
(cherry picked from commit 7057fe8630079bf778dfa7d3ba841515bcc20eab)
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)
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)
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)
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)
It was only described in systemd(1), making it hard to discover.
Fixes#13561.
The same for $SYSTEMD_URLIFY.
I think all the tools whose man pages include less-variables.xml support
those variables.
(cherry picked from commit 339bf2076b3294e5f7b59e84c59ba8c55ded3c25)
Fixes#13756. We were returning things that didn't make much sense:
we would always use the exit_code value as the exit code. But it sometimes
contains a exit code from the process, and sometimes the number of a signal
that was used to kill the process. We would also ignore SuccessExitStatus=
and in general whether systemd thinks the service exited successfully
(hence the issue in #13756, where systemd would return success/SIGTERM,
but we'd just look at the SIGTERM part.)
If we are doing --wait, let's always propagate the exit code/status from
the child.
While at it, make the documentation useful.
(cherry picked from commit 7f3614e5479446bbd5a2bdf6aed4962e8d803e35)
We want users to use Wants, but we'd describe Requires first and ask users to
look for Wants instead. While at it, let's split the wall of text into sensible
paragraphs: syntax first, followed by semantics and longer description, and
finally hints and comparison to other configuration items last.
(cherry picked from commit d19cd71a8a6dca4565d7d1c8766127b70c10ebe0)
The value is obviously bogus, but didn't seem to cause problems so far.
With meson-0.52.0, it causes a hang. The number of aliases is always rather
small (usually just one or two, possibly up to a dozen in a few cases), so
even if this causes some looping, it is strange that it has such a huge impact.
But let's just remove it.
Fixes#13742.
Tested with meson-0.52.0-1.module_f31+6771+f5d842eb.noarch,
meson-0.51.1-1.fc29.noarch.
(cherry picked from commit af336643a01d0b210b18312c253a50594ba54b0a)
Destination file needs to be a valid hostname and underscores
are not valid hostname characters.
Closes#13542
(cherry picked from commit b12a67ae145ce01d3dc97fc76fed8c1698125dc6)
The docs just tautologically call this the "high limit". Just call it
throttling as we do in cgroup-v2.rst.
(cherry picked from commit ba79e19cb299623c9c0dd4c6a1ae80f795409b04)
I got asked why Memory{Low,Min} don't allow "infinity". They do, but the
docs don't say that like they already do for Memory{High,Max}.
(cherry picked from commit b62087d4d06777ccde9eb9e7a97abc7b8945d5f5)
systemctl supports runlevel invocation name without utmp.
The runlevel symlink is installed unconditionally.
So it's reasonable to install runlevel manpage with it as well.
Signed-off-by: Jan Chren (rindeal) <dev.rindeal@gmail.com>
Traditionally, user logins had a $PATH in which /bin was before /sbin, while
root logins had a $PATH with /sbin first. This allows the tricks that
consolehelper is doing to work. But even if we ignore consolehelper, having the
path in this order might have been used by admins for other purposes, and
keeping the order in user sessions will make it easier the adoption of systemd
user sessions a bit easier.
Fixes#733.
https://bugzilla.redhat.com/show_bug.cgi?id=1744059
OOM handling in manager_default_environment wasn't really correct.
Now the (theorertical) malloc failure in strv_new() is handled.
Please note that this has no effect on:
- systems with merged /bin-/sbin (e.g. arch)
- when there are no binaries that differ between the two locations.
E.g. on my F30 laptop there is exactly one program that is affected:
/usr/bin/setup -> consolehelper.
There is less and less stuff that relies on consolehelper, but there's still
some.
So for "clean" systems this makes no difference, but helps with legacy setups.
$ dnf repoquery --releasever=31 --qf %{name} --whatrequires usermode
anaconda-live
audit-viewer
beesu
chkrootkit
driftnet
drobo-utils-gui
hddtemp
mate-system-log
mock
pure-ftpd
setuptool
subscription-manager
system-config-httpd
system-config-rootpassword
system-switch-java
system-switch-mail
usermode-gtk
vpnc-consoleuser
wifi-radar
xawtv
