{"id":34961,"date":"2019-10-31T22:01:33","date_gmt":"2019-10-31T19:01:33","guid":{"rendered":"https:\/\/prohoster.info\/blog\/vypusk-earlyoom-1-3-protsessa-dlya-rannego-reagirovaniya-na-nehvatku-pamyati\/"},"modified":"2019-10-31T22:01:33","modified_gmt":"2019-10-31T19:01:33","slug":"vypusk-earlyoom-1-3-protsessa-dlya-rannego-reagirovaniya-na-nehvatku-pamyati","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-earlyoom-1-3-protsessa-dlya-rannego-reagirovaniya-na-nehvatku-pamyati","title":{"rendered":"Release of earlyoom 1.3, a process for rapid response to memory shortages","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

After seven months of development has been published<\/a><\/noindex> the release of the background process earlyoom 1.3<\/a><\/noindex>, which periodically checks the available memory (MemAvailable, SwapFree) and attempts to respond at an early stage to memory shortages.<\/p>\n

If the amount of available memory is below a specified value, earlyoom forcibly (by sending SIGTERM or SIGKILL) terminates the process that is consuming the most memory (the one with the highest value in \/proc\/*\/oom_score), without allowing the system to reach a state where its buffers are cleared and hindering swap operation (the OOM (Out Of Memory) handler in the kernel is triggered when the memory shortage condition has already reached critical levels and usually by that point the system is unresponsive to user actions).<\/p>\n

Earlyoom supports sending notifications about forcibly terminated processes to the desktop (using notify-send), and also provides the ability to define rules where process names can be specified using regular expressions for which termination is preferable (the «—prefer» option) or whose stopping should be avoided (the «—avoid» option).<\/p>\n

Key changes in the new release: <\/p>\n