0dd82dab91
openat() will always resolve symlinks, except if O_NOFOLLOW is passed or O_CREAT|O_EXCL is passed. This means that if a dangling symlink is passed to openat_report_new(), the first call to openat() will always fail with ENOENT and the second call to openat() will always fail with EEXIST. Let's catch this case explicitly and fallback to creating the file with just O_CREAT and assume we're the ones that created the file. We can't resolve the symlink with chase() because this function is itself called by chase() so we could end up in weird recursive calls if we'd try to do so.
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, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack