007ef4ea89
When iterating journal entries with --until (forward scan) or --since (reverse scan), the code used continue instead of break after crossing the time boundary. Since sd_journal_seek_realtime_usec() is called before the loop to position at the start of the range, sd_journal_next()/previous() returns entries in monotonically increasing/decreasing time order. Once an entry's timestamp exceeds arg_until (or falls below arg_since in reverse), all subsequent entries will also be out of range. Using continue caused the entire remaining journal to be scanned unnecessarily. journalctl uses break for the identical pattern in src/journal/journalctl-show.c. Fixes: #42808 Signed-off-by: dongshengyuan <dongshengyuan@uniontech.com> (cherry picked from commitbd1bb49ffa) (cherry picked from commit1f720ac2dd)
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
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release