Rivoreo Source Code Repositories
src.rivoreo.one / systemd-stable / v239-8
commite0f2dd42fb02aa5767d38714c95ac10fb683ad67[log] [download]
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>Fri Mar 11 17:06:17 2016 -0500
committerLukas Nykryn <lnykryn@redhat.com>Mon Oct 29 10:41:48 2018 +0100
tree687347877baa37c616668583503d190f4aa98591
parent80d5f0e2057717e9e5588edcabac95b8c238795c [diff]
resolved: create /etc/resolv.conf symlink at runtime

If the symlink doesn't exists, and we are being started, let's
create it to provie name resolution.

If it exists, do nothing. In particular, if it is a broken symlink,
we cannot really know if the administator configured it to point to
a location used by some service that hasn't started yet, so we
don't touch it in that case either.

https://bugzilla.redhat.com/show_bug.cgi?id=1313085
2 files changed
tree: 687347877baa37c616668583503d190f4aa98591
  1. .dir-locals.el
  2. .editorconfig
  3. .gitattributes
  4. .github/
  5. .gitignore
  6. .mailmap
  7. .mkosi/
  8. .travis.yml
  9. .vimrc
  10. .ycm_extra_conf.py
  11. LICENSE.GPL2
  12. LICENSE.LGPL2.1
  13. Makefile
  14. NEWS
  15. README
  16. README.md
  17. TODO
  18. catalog/
  19. coccinelle/
  20. configure
  21. doc/
  22. factory/etc/
  23. hwdb/
  24. man/
  25. meson.build
  26. meson_options.txt
  27. mkosi.build
  28. mkosi.default ⇨ .mkosi/mkosi.fedora
  29. modprobe.d/
  30. network/
  31. po/
  32. presets/
  33. rules/
  34. shell-completion/
  35. src/
  36. sysctl.d/
  37. sysusers.d/
  38. test/
  39. tmpfiles.d/
  40. tools/
  41. travis-ci/
  42. units/
  43. xorg/
  44. zanata.xml
README.md

systemd - System and Service Manager

Build Status
Coverity Scan Status
CII Best Practices
Build Status

Details

General information about systemd can be found in the systemd Wiki.

Information about build requirements are 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 file for information 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.