Rivoreo Source Code Repositories
src.rivoreo.one / systemd-stable / refs/tags/v246.8
tag3d169b2c23e0ab450c865213b68c4f8c169333cc
taggerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>Wed Dec 16 14:35:33 2020 +0100
objecte39f0fa5c3da64181981ee9dc373b400e6453b19 
systemd-stable v246.8
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXCUbX8VOsvgPQHqqxUyjNs/rVX4FAl/aDSUACgkQxUyjNs/r
VX6gHA//Tbn/LJlJTS3ngw514qOMtMiqdm2g7gEnblic540pR/vyjBlTgIh8NVLr
f6ZHYMic6kE5Y1Xf0ADwA8baTWsMTPLUcqxrcFlEQFQTN0y6zPCFJ3D61WwaxzkI
QVt/9tc4pcsI6dmNLk2+6ak1ik4YondTV/deWNSsKWCEPfHoqDyndl650VFiaZna
at7bAGUebs+WMrbIY3Xi5qUjvTbrL3hZWFUZeGfvbhHFa7TqggLTztNOshpWtc5b
gqnvh6dUiAc41pJx0GNyDE59ailq7nZZcWdfDENN9TPNraA1qhilzVuWRIFAJEiF
A94WU0aDGx1MPjWcdf05gfqGEPolo/dA3WAMExByNrJMq9K6xZloj6B3xf1vFzTI
hi8Gj0OoPbyTzwUrsAF+d+b2Ww7sRPxWwfMy2wkqdgihJxBVb860cQVaaeN4Z4aZ
c/SBs2DaQQt+exzXVahUXSZkFJM3CO+UBCXihSxnBj7k2zFS6s5JK2YKmS49EdSc
pq/KlDvt9T3A3SOJYvNM3sqyjrAbXeN6+QqfvP0C43N7DRx3keYlJhK7Or8LbZjk
pK4k66WyLFhe16Ddn2fZsr5Mb47c0FaIt1MB/OQYTk4a1mDs6oa930Vvyrj8s2Qg
U0fzoWrKkuYGLHJ+CExYzMrV2uvGpcoq/S42Wj1g616fynYaGsk=
=Od9q
-----END PGP SIGNATURE-----
commite39f0fa5c3da64181981ee9dc373b400e6453b19[log] [download]
authorYu Watanabe <watanabe.yu+github@gmail.com>Mon Nov 16 16:25:43 2020 +0900
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>Wed Dec 16 14:34:54 2020 +0100
tree4ae1c9979c365148767d019748eb0b6afa0a05a2
parent83c47527396842302154203fbb5ada66747d0175 [diff]
network: honor M or O flag in RA even if IPv6AcceptRA.DHCPv6Cleint=always

Follow-up for ac24e418d9bc988ecf114c464701b35934948178.

The original motivation of the commit and RFE #15339 is to start dhcpv6
client in managed mode when neither M nor O flag is set in the RA.
But, previously, if the setting is set to "always", then the DHCPv6
client is always started in managed mode even if O flag is set in the
RA. Such the behavior breaks RFC 7084.

(cherry picked from commit 0e686feaff71465e3220f234871f66a39f0f57ad)
2 files changed
tree: 4ae1c9979c365148767d019748eb0b6afa0a05a2
  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.