Repository navigation
Keep a service's own lower OOM score - #12
Merged
Merged
Conversation
Debian's PostgreSQL unit sets OOMScoreAdjust=-900; genco's drop-in replaced that with -600 at its next start (seen on gs3 after 0.13.0), less protection than before. A unit whose own file sets -600 or lower gets no drop-in now, an old one of genco's is removed, and its running processes keep (or get back) its own score. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A unit that sets its own lower score (Debian's PostgreSQL) only gets it back on processes still at genco's old -600: its backends reset themselves to 0 so a runaway query is killed first, and pushing them to -900 would make the kernel pick nginx or mail instead. Unit files with spaces around the = are read too, and a drop-in that can't be removed is reported. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
noah-meierlabs
added a commit
that referenced
this pull request
Nov 14, 2026
OPERATIONS.md still said every shared service gets -600; since #12 a unit with a lower score of its own (PostgreSQL's -900) keeps it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
noah-meierlabs
added a commit
that referenced
this pull request
Nov 14, 2026
* Release 0.13.1 PostgreSQL keeps its own stronger OOM protection instead of genco's drop-in value. Plans are short enough to read in under a minute (at most 1500 characters). The taskbar also shows proposals still being planned. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Document that services keep their own lower OOM score OPERATIONS.md still said every shared service gets -600; since #12 a unit with a lower score of its own (PostgreSQL's -900) keeps it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.
After 0.13.0, gs3's PostgreSQL went from Debian's -900 to genco's -600 (the drop-in replaced the unit's own OOMScoreAdjust at its next start). Units whose own file (or template, for postgresql@17-main) sets -600 or lower now get no drop-in, an old genco drop-in is removed (daemon-reload), and their running processes keep or get back the unit's own score. Tested on the test server: drop-in gone, postgresql@17-main OOMScoreAdjust and process at -900, mariadb still -600.
🤖 Generated with Claude Code