journalctl: allow running vacuum on remote journals, too#13924
Merged
poettering merged 1 commit intosystemd:masterfrom Nov 4, 2019
Merged
journalctl: allow running vacuum on remote journals, too#13924poettering merged 1 commit intosystemd:masterfrom
poettering merged 1 commit intosystemd:masterfrom
Conversation
Right now the `systemd-journal-remote` service does not constrain its resource usage (I just run out of space on my 100GB partition, for example). This patch does not change that, but it at least makes it possible to run something like: journalctl --directory /var/log/journal/remote --rotate --vacuum-size=90G fixes systemd#2376 Co-authored-by: Mike Auty <[email protected]>
poettering
added
the
good-to-merge/waiting-for-ci 👍
keszybz
removed
the
good-to-merge/waiting-for-ci 👍
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Right now the
systemd-journal-remoteservice does not constrain its resource usage (I just run out of space on my 100GB partition, for example). This patch does not change that, but it at least makes it possible to run something like:fixes #2376
Tested on a Fedora 31: built the code, and then running something like
SYSTEMD_LOG_LEVEL=debug /pth/to/my/systemd/build/journalctl --directory /var/log/journal/remote --rotate --vacuum-size=2Gsays that it is removing files, and I now have more free space. Thanks to @ikelos for the initial idea.