Re:When the memory allocator works against you
by deathanatos on Sunday March 12, 2017 @05:52PM
(#13853350)
> Something that is annoying: as far as I know there is no signal that fires when this happens. Instead, you scrape logs to learn about it. Whereupon you will reboot the box, because you no longer trust its state. You can get a callback when this happens if you use systemtap.
It's a SIGKILL, which isn't catchable/handleable by the process (how could it be?).
The machine should still be stable after an OOM, just minus a few process. (In my production setups, usually a supervising daemon can restart the now-dead child, and begin the memory leaking cycle anew.)
It's a SIGKILL, which isn't catchable/handleable by the process (how could it be?).
The machine should still be stable after an OOM, just minus a few process. (In my production setups, usually a supervising daemon can restart the now-dead child, and begin the memory leaking cycle anew.)