ab8f553d1e
- Rename generic_array_bisect_one() -> generic_array_bisect_step(), as there is also generic_array_bisect_plus_one(), so the original name is confusing. - Make generic_array_bisect_step() return TEST_GOTO_NEXT or TEST_GOTO_PREVIOUS when the current array does not contain any matching entries. - Make generic_array_bisect_step() symmetric with respect to the direction we are going to, except for the journal corruption handling. - Make generic_array_bisect_step() gracefully handle journal corruptions, so the corruption handling in the caller side can be mostly dropped. - Especially, when the last entry in an array is corrupted, previously we tried to find a valid entry sequentially from the end of the array, but now we anyway bisect the array. That should improve performance of reading corrupted journal files. - Return earlier when no entry linked to the chained array (n == 0). - Add many comments. No behavior change unless journal is corrupted. |
||
---|---|---|
.clusterfuzzlite | ||
.github | ||
.semaphore | ||
catalog | ||
coccinelle | ||
docs | ||
factory | ||
hwdb.d | ||
LICENSES | ||
man | ||
mkosi.conf.d | ||
mkosi.presets | ||
modprobe.d | ||
network | ||
po | ||
presets | ||
rules.d | ||
shell-completion | ||
src | ||
sysctl.d | ||
sysusers.d | ||
test | ||
tmpfiles.d | ||
tools | ||
units | ||
xorg | ||
.clang-format | ||
.ctags | ||
.dir-locals.el | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
.packit.yml | ||
.pylintrc | ||
.vimrc | ||
.ycm_extra_conf.py | ||
configure | ||
LICENSE.GPL2 | ||
LICENSE.LGPL2.1 | ||
Makefile | ||
meson.build | ||
meson_options.txt | ||
mkosi.kernel.config | ||
NEWS | ||
README | ||
README.md | ||
TODO |
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.