We would try to return a value that could be nonzero only if the kernel reported writing more bytes than we gave to it, hopefully a rare occurence. Instead, assert that this doesn't happen. Instead, return true if we got to the end of the iovec array. The caller can use this information to know that the whole iovec array was written. This allows one loop to be dropped in write_to_syslog(). Also drop _unlikely_: this function is called with very short arrays, and it *is* likely that we trigger this condition. Let's just let the compiler generate normal code without giving it a potentially false hint.
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 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.
