systemd-stable v246.9
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXCUbX8VOsvgPQHqqxUyjNs/rVX4FAl/aQ0cACgkQxUyjNs/r
VX5++w/8COuwVr1zOwWyAm3rD/5FYfDSbe1wFZjLJyoNMMZ8EXUjf6GqYLHiFgdU
2Mu9/A6dhG4fEbFjXWvZvxkkyfxeQk+32RS9jB+iqiT3cGiDu6aIAZpqvKy3u9QE
mt/BCMr9mlBUR4Oc1hLAzY4UBT1WonZdUSTZL3rOghz/MEyVPhYhzh8EJ/Y5ADFY
GqiQd2XUx6Py98WyfkQGktCHzDSSTc/k+InrpnsLUnVrDqTKnI0C5C/Huu9CeapZ
YZCm2QGp18yO1VqblMt7wXh00e2sLDk7HVTuMOFWzQo9HQpecqyB5dn+PqlX7hVl
l3l83G5o7BKBd8rCwE0PPptdJNj3HQYKVicptOLV4UvYUYv5SpiqEw36gYj5UcfH
vjVGmt0y6pjVcONB+/AGhqbZP7pwjmbH/obcJ/629CF2o5icBQp4aX1jpE69e5S1
Zz24mevWAUOD5fIHQnWlB4bAA2uVqxfm9Zy0c9eGdezD8alHvDRDP2INF7ozG4eR
n+/D6lajihSt8DIbz3hvEla/OSjv/UIjaKscem50+HjBNvBm8YXzVXEKu3RGl2ld
xVWMfBTGGOQKJ+ZfKCT3AgzNRtOlwIx+YFuXbRgmh8CBk3nnwxfpfX2Kqubm+2xN
93KQsQieMBNB6Zp8YxEtt3Ze/fu5MLFkIp90V01OAX5a0dnr7EY=
=jyL3
-----END PGP SIGNATURE-----
test-login: skip consistency checks when logind is not active

There are two ways in swich sd_login_* functions acquire data:
some are derived from the cgroup path, but others use the data serialized
by logind.

When the tests are executed under Fedora's mock, without systemd-spawn
but instead in a traditional chroot, test-login gets confused:
the "outside" cgroup path is visible, so sd_pid_get_unit() and
sd_pid_get_session() work, but sd_session_is_active() and other functions
that need logind data fail.

Such a buildroot setup is fairly bad, but it can be encountered in the wild, so
let's just skip the tests in that case.

/* Information printed is from the live system */
sd_pid_get_unit(0, …) → "session-237.scope"
sd_pid_get_user_unit(0, …) → "n/a"
sd_pid_get_slice(0, …) → "user-1000.slice"
sd_pid_get_session(0, …) → "237"
sd_pid_get_owner_uid(0, …) → 1000
sd_pid_get_cgroup(0, …) → "/user.slice/user-1000.slice/session-237.scope"
sd_uid_get_display(1000, …) → "(null)"
sd_uid_get_sessions(1000, …) → [0] ""
sd_uid_get_seats(1000, …) → [0] ""
Assertion 'r >= 0' failed at src/libsystemd/sd-login/test-login.c:104, function test_login(). Aborting.

(cherry picked from commit ac5644635dba54ce5eb0ff394fc0bc772a984849)
(based on 4275f1c95e730ca9422463be29747ad4b6b1fb91)
1 file changed
tree: ab6cf4d7a097bb12419bfef796f5f9e077720c11
  1. .clang-format
  2. .ctags
  3. .dir-locals.el
  4. .editorconfig
  5. .gitattributes
  6. .github/
  7. .gitignore
  8. .lgtm.yml
  9. .lgtm/cpp-queries/
  10. .mailmap
  11. .mkosi/
  12. .travis.yml
  13. .vimrc
  14. .ycm_extra_conf.py
  15. LICENSE.GPL2
  16. LICENSE.LGPL2.1
  17. Makefile
  18. NEWS
  19. README
  20. README.md
  21. TODO
  22. azure-pipelines.yml
  23. catalog/
  24. coccinelle/
  25. configure
  26. docs/
  27. factory/etc/
  28. hwdb.d/
  29. man/
  30. meson.build
  31. meson_options.txt
  32. mkosi.build
  33. modprobe.d/
  34. network/
  35. po/
  36. presets/
  37. rules.d/
  38. semaphoreci/
  39. shell-completion/
  40. src/
  41. sysctl.d/
  42. sysusers.d/
  43. test/
  44. tmpfiles.d/
  45. tools/
  46. travis-ci/
  47. units/
  48. xorg/
  49. zanata.xml
README.md

Systemd

System and Service Manager

Semaphore CI Build Status
Coverity Scan Status
OSS-Fuzz Status
CIFuzz
CII Best Practices
Travis CI Build Status
Language Grade: C/C++
CentOS CI Build Status
Build Status
Fossies codespell report Packaging status

Details

Most documentation is available on systemd's web site.

Assorted, older, general information about systemd can be found in the systemd Wiki.

Information about build requirements is provided in the README file.

Consult our NEWS file for information about what's new in the most recent systemd versions.

Please see the Hacking guide for information on how to hack on systemd and test your modifications.

Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.

When preparing patches for systemd, please follow our Coding Style Guidelines.

If you are looking for support, please contact our mailing list or join our IRC channel.

Stable branches with backported patches are available in the stable repo.