Gentoo Packages

Search

Install

Install this package:

emerge -a sys-apps/earlyoom

If the package is masked, you can unmask it using the autounmask tool or standard emerge options:

autounmask sys-apps/earlyoom

Or alternatively:

emerge --autounmask-write -a sys-apps/earlyoom

Package Information

Description:

The oom-killer generally has a bad reputation among Linux users. One may have to sit in front of an unresponsive system, listening to the grinding disk for minutes, and press the reset button to quickly get back to what one was doing after running out of patience. Earlyoom checks the amount of available memory and free swap up to 10 times a second (less often if there is a lot of free memory). If both memory and swap are below 10%, it will kill the largest process (highest oom_score). The percentage value is configurable via command line arguments. If there is a failure when trying to kill a process, earlyoom sleeps for 1 second to limit log spam due to recurring errors.

Homepage:

https://github.com/rfjakob/earlyoom

License:

MIT

Versions

Metadata

Description

• The oom-killer generally has a bad reputation among Linux users. One may have to sit in front of an unresponsive system, listening to the grinding disk for minutes, and press the reset button to quickly get back to what one was doing after running out of patience. Earlyoom checks the amount of available memory and free swap up to 10 times a second (less often if there is a lot of free memory). If both memory and swap are below 10%, it will kill the largest process (highest oom_score). The percentage value is configurable via command line arguments. If there is a failure when trying to kill a process, earlyoom sleeps for 1 second to limit log spam due to recurring errors.

Maintainers

• saniter (saniter.dev@outlook.com) - Type: person

Upstream

• Remote IDs:
  • github: rfjakob/earlyoom

<pkgmetadata>
	<maintainer type="person">
		<email>saniter.dev@outlook.com</email>
		<name>saniter</name>
	</maintainer>
	<longdescription lang="en">
    The oom-killer generally has a bad reputation among Linux users. One may have to sit in front of an unresponsive system, listening to the grinding disk for minutes, and press the reset button to quickly get back to what one was doing after running out of patience.
    Earlyoom checks the amount of available memory and free swap up to 10 times a second (less often if there is a lot of free memory). If both memory and swap are below 10%, it will kill the largest process (highest oom_score). The percentage value is configurable via command line arguments.
    If there is a failure when trying to kill a process, earlyoom sleeps for 1 second to limit log spam due to recurring errors.
  </longdescription>
	<upstream>
		<remote-id type="github">rfjakob/earlyoom</remote-id>
	</upstream>
</pkgmetadata>

Lint Warnings

• [Warning] USE flag 'man' in ebuild 1.9.0 is not documented in metadata.xml
• [Error] Missing md5-cache for ebuild earlyoom-1.9.0

USE Flags

Manage flags for this package: euse -i <flag> -p sys-apps/earlyoom | euse -E <flag> -p sys-apps/earlyoom | euse -D <flag> -p sys-apps/earlyoom

Files

• earlyoom-r1

Manifest