Repository navigation
Conversation
|
Reviewed da3d977 (architecture, correctness, lifetimes, security, style, tests). All findings are resolved 🎉 Suggestions
|
With CPU/I/O accounting enabled, inherited pressure parameters prevent the user manager from setting its own threshold, producing: systemd[807]: Failed to adjust io pressure threshold, ignoring: Device or resource busy Use CPU/IOPressureWatch=skip, as for memory pressure, so the user manager and capsule manager configure monitoring for their own init.scope. Follow-up for 9d03637
bluca
force-pushed
the
user_io_pressure
branch
from
October 24, 2026 00:26
ba15225 to
da3d977
Compare
This branch has not been deployed
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
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.
With I/O accounting enabled, inherited pressure parameters prevent the user manager from setting its own threshold, producing:
Use IOPressureWatch=skip, as for memory pressure, so the user manager configures monitoring for its own init.scope.
Follow-up for 9d03637