OOMD​.CONF - Online Linux Manual PageSection : 5
Updated :
Source : systemd 253
Note : oomd.conf

NAMEoomd.conf, oomd.conf.d − Global systemd−oomd configuration files

SYNOPSIS/etc/systemd/oomd​.conf /etc/systemd/oomd​.conf​.d/*​.conf /usr/lib/systemd/oomd​.conf​.d/*​.conf

DESCRIPTIONThese files configure the various parameters of the systemd(1) userspace out−of−memory (OOM) killer, systemd-oomd.service(8)​. See systemd.syntax(7) for a general description of the syntax​.

CONFIGURATION DIRECTORIES AND PRECEDENCEThe default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults​. Initially, the main configuration file in /etc/systemd/ contains commented out entries showing the defaults as a guide to the administrator​. Local overrides can be created by editing this file or by creating drop−ins, as described below​. Using drop−ins for local configuration is recommended over modifications to the main configuration file​. In addition to the "main" configuration file, drop−in configuration snippets are read from /usr/lib/systemd/*​.conf​.d/, /usr/local/lib/systemd/*​.conf​.d/, and /etc/systemd/*​.conf​.d/​. Those drop−ins have higher precedence and override the main configuration file​. Files in the *​.conf​.d/ configuration subdirectories are sorted by their filename in lexicographic order, regardless of in which of the subdirectories they reside​. When multiple files specify the same option, for options which accept just a single value, the entry in the file sorted last takes precedence, and for options which accept a list of values, entries are collected as they occur in the sorted files​. When packages need to customize the configuration, they can install drop−ins under /usr/​. Files in /etc/ are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages​. Drop−ins have to be used to override package drop−ins, since the main configuration file has lower precedence​. It is recommended to prefix all filenames in those subdirectories with a two−digit number and a dash, to simplify the ordering of the files​. To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to /dev/null in the configuration directory in /etc/, with the same filename as the vendor configuration file​.

[OOM] SECTION OPTIONSThe following options are available in the [OOM] section: SwapUsedLimit= Sets the limit for memory and swap usage on the system before systemd−oomd will take action​. If the fraction of memory used and the fraction of swap used on the system are both more than what is defined here, systemd−oomd will act on eligible descendant control groups with swap usage greater than 5% of total swap, starting from the ones with the highest swap usage​. Which control groups are monitored and what action gets taken depends on what the unit has configured for ManagedOOMSwap=​. Takes a value specified in percent (when suffixed with "%"), permille ("") or permyriad (""), between 0% and 100%, inclusive​. Defaults to 90%​. DefaultMemoryPressureLimit= Sets the limit for memory pressure on the unit's control group before systemd−oomd will take action​. A unit can override this value with ManagedOOMMemoryPressureLimit=​. The memory pressure for this property represents the fraction of time in a 10 second window in which all tasks in the control group were delayed​. For each monitored control group, if the memory pressure on that control group exceeds the limit set for longer than the duration set by DefaultMemoryPressureDurationSec=, systemd−oomd will act on eligible descendant control groups, starting from the ones with the most reclaim activity to the least reclaim activity​. Which control groups are monitored and what action gets taken depends on what the unit has configured for ManagedOOMMemoryPressure=​. Takes a fraction specified in the same way as SwapUsedLimit= above​. Defaults to 60%​. DefaultMemoryPressureDurationSec= Sets the amount of time a unit's control group needs to have exceeded memory pressure limits before systemd−oomd will take action​. Memory pressure limits are defined by DefaultMemoryPressureLimit= and ManagedOOMMemoryPressureLimit=​. Must be set to 0, or at least 1 second​. Defaults to 30 seconds when unset or 0​.

SEE ALSOsystemd(1), systemd.resource-control(5), systemd-oomd.service(8), oomctl(1)
0
Johanes Gumabo
Data Size   :   11,301 byte
man-oomd.conf.d.5Build   :   2024-12-05, 20:55   :  
Visitor Screen   :   x
Visitor Counter ( page / site )   :   3 / 200,945
Visitor ID   :     :  
Visitor IP   :   3.145.81.47   :  
Visitor Provider   :   AMAZON-02   :  
Provider Position ( lat x lon )   :   39.962500 x -83.006100   :   x
Provider Accuracy Radius ( km )   :   1000   :  
Provider City   :   Columbus   :  
Provider Province   :   Ohio ,   :   ,
Provider Country   :   United States   :  
Provider Continent   :   North America   :  
Visitor Recorder   :   Version   :  
Visitor Recorder   :   Library   :  
Online Linux Manual Page   :   Version   :   Online Linux Manual Page - Fedora.40 - march=x86-64 - mtune=generic - 24.12.05
Online Linux Manual Page   :   Library   :   lib_c - 24.10.03 - march=x86-64 - mtune=generic - Fedora.40
Online Linux Manual Page   :   Library   :   lib_m - 24.10.03 - march=x86-64 - mtune=generic - Fedora.40
Data Base   :   Version   :   Online Linux Manual Page Database - 24.04.13 - march=x86-64 - mtune=generic - fedora-38
Data Base   :   Library   :   lib_c - 23.02.07 - march=x86-64 - mtune=generic - fedora.36

Very long time ago, I have the best tutor, Wenzel Svojanovsky . If someone knows the email address of Wenzel Svojanovsky , please send an email to johanes_gumabo@yahoo.co.id .
If error, please print screen and send to johanes_gumabo@yahoo.co.id
Under development. Support me via PayPal.