-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
What about SIGTERM? #67
Comments
I expect the follow behavior by default: 10% - SIGTERM, 5% - SIGKILL. Code like this
|
Do you know an app that does something useful on SIGTERM? |
I didn't understand what you meant. I know that most of apps accept SIGTERM and terminate correctly. |
The disadvantage is that SIGTERM can be ignored by apps. What is the advantage? |
I guess the idea is that the app does something like "clean up before shutdown". However, how long does that take? Does it need additional memory to do so? |
It happens quickly in most cases. Even it will need additional memory, process will killed at 5% (for example). Also, user will can set thresholds like that: 10% for SIGKILL and 0% for SIGTERM for ignore SIGTERM. |
The thing is, this is an extra option that the user may have to think about. earlyoom only uses sigkill and works fine! |
Should I stop offer any features more? |
I think that users are not idiots. |
No, don't stop! I like several of them. |
I am going through old tickets, and read this #34 again. Apparently postgresql does something useful on SIGTERM. I'll think again about this. |
2018 will end soon, but the signal is still not supported.
The text was updated successfully, but these errors were encountered: