Lennart Poettering
5a3627e511
Somehow the Linux kernel allows us to allocate a network namespace if we possess CAP_SYS_ADMIN but doesn't allow us to configure it, unless we also have CAP_NET_ADMIN. Taking that into consideration let's avoid allocating a network namespace we cannot even configure "lo" in. This is common case if nspawn is invoked without userns and without netns, because in that case it will have CAP_SYS_ADMIN but no CAP_NET_ADMIN. This also takes down a notch the messages about the automatic downgrading. These have been LOG_WARNING so far, and I downgraded them to LOG_NOTICE, since in an environment where CAP_NET_ADMIN is not available this is really not something to be concerned about, but still noticable. With that it's still more priorized than regular LOG_INFO. Fixes: #27292
System and Service Manager
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 Code Map for information about this repository's layout and content.
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.