Early OOM, also known as Earlyoom, is a minimalist out of memory (OOM) daemon that runs in user space and provides a more responsive and configurable alternative to the in-kernel OOM killer. It is useful to prevent the system from becoming unresponsive when it runs out of memory.
The service type for running
earlyoom, the Early OOM daemon.
Its value must be a
earlyoom-configuration object, described
below. The service can be instantiated in its default configuration
This is the configuration record for the
The Earlyoom package to use.
The threshold for the minimum available memory, in percentages.
The threshold for the minimum free swap memory, in percentages.
A regular expression (as a string) to match the names of the processes that should be preferably killed.
A regular expression (as a string) to match the names of the processes that should not be killed.
The interval in seconds at which a memory report is printed. It is disabled by default.
A boolean indicating whether the positive adjustments set in /proc/*/oom_score_adj should be ignored.
A boolean indicating whether debug messages should be printed. The logs are saved at /var/log/earlyoom.log.
This can be used to provide a custom command used for sending notifications.
The kernel module loader service allows one to load loadable kernel
modules at boot. This is especially useful for modules that don’t
autoload and need to be manually loaded, as is the case with
The service type for loading loadable kernel modules at boot with
modprobe. Its value must be a list of strings representing
module names. For example loading the drivers provided by
ddcci-driver-linux, in debugging mode by passing some module
parameters, can be done as follow:
(use-modules (gnu) (gnu services)) (use-package-modules linux) (use-service-modules linux) (define ddcci-config (plain-file "ddcci.conf" "options ddcci dyndbg delay=120")) (operating-system ... (services (cons* (service kernel-module-loader-service-type '("ddcci" "ddcci_backlight")) (simple-service 'ddcci-config etc-service-type (list `("modprobe.d/ddcci.conf" ,ddcci-config))) %base-services)) (kernel-loadable-modules (list ddcci-driver-linux)))
The Rasdaemon service provides a daemon which monitors platform RAS (Reliability, Availability, and Serviceability) reports from Linux kernel trace events, logging them to syslogd.
Reliability, Availability and Serviceability is a concept used on servers meant to measure their robustness.
Relability is the probability that a system will produce correct outputs:
Availability is the probability that a system is operational at a given time:
Serviceability is the simplicity and speed with which a system can be repaired or maintained:
Among the monitoring measures, the most usual ones include:
By monitoring the number of occurrences of error detections, it is possible to identify if the probability of hardware errors is increasing, and, on such case, do a preventive maintenance to replace a degraded component while those errors are correctable.
For detailed information about the types of error events gathered and how to make sense of them, see the kernel administrator’s guide at https://www.kernel.org/doc/html/latest/admin-guide/ras.html.
Service type for the
rasdaemon service. It accepts a
rasdaemon-configuration object. Instantiating like
will load with a default configuration, which monitors all events and logs to syslogd.
The data type representing the configuration of
A boolean indicating whether to record the events in an SQLite database. This provides a more structured access to the information contained in the log file. The database location is hard-coded to /var/lib/rasdaemon/ras-mc_event.db.
The Zram device service provides a compressed swap device in system memory. The Linux Kernel documentation has more information about zram devices.
This service creates the zram block device, formats it as swap and
enables it as a swap device. The service’s value is a
This is the data type representing the configuration for the zram-device service.
This is the amount of space you wish to provide for the zram device. It
accepts a string and can be a number of bytes or use a suffix, eg.:
This is the compression algorithm you wish to use. It is difficult to
list all the possible compression options, but common ones supported by
Guix’s Linux Libre Kernel include
This is the maximum amount of memory which the zram device can use.
Setting it to ’0’ disables the limit. While it is generally expected
that compression will be 2:1, it is possible that uncompressable data
can be written to swap and this is a method to limit how much memory can
be used. It accepts a string and can be a number of bytes or use a
This is the priority of the swap device created from the zram device. See Swap Space for a description of swap priorities. You might want to set a specific priority for the zram device, otherwise it could end up not being used much for the reasons described there.