Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFE: a tiny helper tool for adjusting "oom_score_adj" #609

Closed
poettering opened this issue Mar 27, 2018 · 2 comments
Closed

RFE: a tiny helper tool for adjusting "oom_score_adj" #609

poettering opened this issue Mar 27, 2018 · 2 comments

Comments

@poettering
Copy link
Contributor

We have various tools for setting various process parameters with various tools, but there's no nice tool for adjusting the OOM score when executing something. It would be awesome if util-linux would maybe gain a new tiny tool maybe called "choom" for changing the OOM score adjust values. Example:

choom -n 1000 /usr/bin/foo

Or so. or even choom -p 4711 -n 750 for changing the OOM score adjust value for PID 4711 to 750.

i.e. a tool that feels a bit like nice or renice, but adjust the OOM score.

Yes, adjusting the OOM adjust value manually is pretty easy, as you can just echo into it, but it would still be nicer to have a wrapper tool that parses a command line and then execs it.

@karelzak karelzak added the TODO We going to think about it ;-) label Mar 27, 2018
@karelzak
Copy link
Collaborator

Sounds like a good idea.

karelzak added a commit that referenced this issue Mar 27, 2018
Addresses: #609
Signed-off-by: Karel Zak <kzak@redhat.com>
karelzak added a commit that referenced this issue Apr 16, 2018
Let's provide command line tool, man page with OOM description and
bash-completion. It seems better than force end-users to use "echo"
to /proc.

Addresses: #609
Signed-off-by: Karel Zak <kzak@redhat.com>
@karelzak karelzak removed the TODO We going to think about it ;-) label Apr 16, 2018
@poettering
Copy link
Contributor Author

Excellent! thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants