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-analyze plot > test.svg produces output with all y and height
element attributes equal to zero. This of course causes the resulting
svg to appear blank (zero height). Bug does not affect x86. Looks like
a compiler optimization may be the culprit.
https://github.com/archlinuxarm/PKGBUILDs/issues/815
(cherry picked from commit a213b7e977221ca96bbc1b19a5a879c912ba2488)
The tty associated with a VT should be owned by the owner of the session
running on the VT. This is important for supporting a socket activated X
server, since the X server will open the tty itself.
This commit makes sure to chown the tty any time a session is
created and and chown it back to root any time the session
is removed. This behavior is copied from /bin/login.
(cherry picked from commit d6176c6c97bf0614c2e7caaf2156bf813b39337a)
Conflicts:
src/login/logind-session.c
Cases where name_to_handle_at is used allocated the full struct to be
MAX_HANDLE_SZ, and assigned this size to handle_bytes. This is wrong
since handle_bytes should describe the length of the flexible array
member and not the whole struct.
Define a union type which includes sufficient padding to allow
assignment of MAX_HANDLE_SZ to be correct.
(cherry picked from commit 370c860f748d149097710dc7952a64f627db9de7)
Conflicts:
src/shared/util.h
When starting up journald on a new system, set the proper permissions on
the system.journal files, not only on the journal directory.
(cherry picked from commit a606871da508995f5ede113a8fc6538afd98966c)
create_symlink() do not check the return value of unlink(), this may
confuse the user.
Before the unlink() call we check the 'force' argument. If it is not set
we fail with -EEXIST, otherwise we unlink() the file, therefore the next
symlink() should not fail with -EEXIST (do not count races...).
However since callers may not have appropriate privileges to unlink()
the file we lose the -EPERM or any other errno code of unlink(), and
return the -EEXIST of the next symlink(). Fix this by checking unlink()
results.
Before:
$ systemctl --force --root=~/container-03 set-default multi-user.target
Failed to set default target: File exists
After:
$ systemctl --force --root=~/container-03 set-default multi-user.target
Failed to set default target: Permission denied
(cherry picked from commit af7fce1cdb6c0d6ce56bcddccbc31dd3d64a8cd8)
Currently "systemctl set-default" will fail to change the default target
due to the 'default.target' being a symlink which is always the case.
To work around this, the user must specify the "--force" switch to be
able to overwrite the existing symlink.
This is clearly a regression that was introduced by commit 718db96199e
since it worked before without the "--force" switch and the man pages do
not mention that you need to specify it. It is expected that this is a
symlink.
So just explicity set the force flag to make it work again.
https://bugs.freedesktop.org/show_bug.cgi?id=76623
Reported-by: <code@progandy.de>
(cherry picked from commit a1484a216e79da1fa7e2323095fb1b7203fb7a17)
It turns out that plain sysctl understands a.b/c syntax to write to
/proc/sys/a/b.c. Support this for compatibility.
https://bugs.freedesktop.org/show_bug.cgi?id=77466
(cherry picked from commit 2e573fcf8754fdfe0db0a783b1631ec1679b063a)
sec is not set if have_time is false so avoid using it. have_time
was introduced in 9ff09bcb86fb125768667aca9bc0b10b1745370a but only
the first uses for sec were covered
Found with scan-build
(cherry picked from commit 2667cc25896a15f82f9f1583e80d416beb1316e1)
Conflicts:
src/timedate/timedatectl.c
The data in the PCI ids file is randomly inconsistent. Many
subvendor model strings just describe the "product" where the
hardware is built into, not the hardware itself. This causes
some "Network Card Model Foo" to show up as "Laptop Model Bar".
Try to make the best out of this mess and concatenate both
strings to describe the hardware.
(cherry picked from commit d060b62fcb4746d3758c567e9379c6728a035b66)
... it turns out that the duplicates in our own catalog were not real
duplicates, but translations.
(cherry picked from commit baf167ee0a2953f98e4e7d4c35752ef737832674)
- Negative/positive errno mixup caused duplicates not to be detected properly.
Now we get a warning about some duplicate entries in our own catalogs...
- Errors in update_catalog would be ignored, but they should not be.
(cherry picked from commit e3b9d9c8027a7c4c55cf1614e0fe9423fad69e8f)
systemd-machined doesn't store cgroup path in a state file anymore.
Let's figure it out from the scope.
(cherry picked from commit 13be49798cc4d1bdf84780b6a315e920f20fa11a)
Return negative errno in wall_tty_block(). get_ctty_devnr() already
returns a negative errno in case of failure, no need to negate it again.
Reported-by: Simon <hwold@odai.homelinux.net>
(cherry picked from commit ee0e4cca5ac37a094dfe1074907dae70c7b7701c)
In "export" format, newlines are significant, and messages containing
newlines must be exported as "binary".
(cherry picked from commit 0ade5ffe2778e7b238bba8d979ca4d53dee1e702)
If a device is unplugged while we initialize it, we will get ENOENT for
ACL-init (and related stuff). We currently print errors then, which is
misleading. Print a debug-message early and continue.
(cherry picked from commit 8016b904849a2d2bd8b0171ed8493db5524b5ff7)
That way, we don't forget to initialize it when the watchdog is
initialized before all event sources.
(cherry picked from commit 52444dc478fe38b5b69a771923ab429a41927aa5)
Conflicts:
src/libsystemd/sd-event/sd-event.c
A terminated connection is a runtime error and not a developer mistake,
hence don't use assert_return() to check for it.
(cherry picked from commit a3d59cd1b0a2738d06893948492113f2c35be0af)
Conflicts:
src/libsystemd/sd-bus/sd-bus.c
Commit 4a77ca7 was an attempt at fixing the wording of --after and --before,
but the new wording was unclear.
Split the combined --after/--before section into a separate section for
each, explicitly state what each option does, and add information about
how these lists are generated.
Reported-by: Andrey Borzenkov <arvidjaar@gmail.com>
Reported-by: Lennart Poettering <lennart@poettering.net>
(cherry picked from commit 9029f64298cb70c12ecf638fddee7f41b056fcf1)