1OOMD.CONF(5) oomd.conf OOMD.CONF(5)
2
6 oomd.conf, oomd.conf.d - Global systemd-oomd configuration files
7
9 /etc/systemd/oomd.conf
10 /etc/systemd/oomd.conf.d/*.conf
12 /usr/lib/systemd/oomd.conf.d/*.conf
14
16 These files configure the various parameters of the systemd(1)
17 userspace out-of-memory (OOM) killer, systemd-oomd.service(8). See
18 systemd.syntax(7) for a general description of the syntax.
19
21 The default configuration is set during compilation, so configuration
22 is only needed when it is necessary to deviate from those defaults.
23 Initially, the main configuration file in /etc/systemd/ contains
24 commented out entries showing the defaults as a guide to the
25 administrator. Local overrides can be created by editing this file or
26 by creating drop-ins, as described below. Using drop-ins for local
27 configuration is recommended over modifications to the main
28 configuration file.
29 In addition to the "main" configuration file, drop-in configuration
31 snippets are read from /usr/lib/systemd/*.conf.d/,
32 /usr/local/lib/systemd/*.conf.d/, and /etc/systemd/*.conf.d/. Those
33 drop-ins have higher precedence and override the main configuration
34 file. Files in the *.conf.d/ configuration subdirectories are sorted by
35 their filename in lexicographic order, regardless of in which of the
36 subdirectories they reside. When multiple files specify the same
37 option, for options which accept just a single value, the entry in the
38 file sorted last takes precedence, and for options which accept a list
39 of values, entries are collected as they occur in the sorted files.
40 When packages need to customize the configuration, they can install
42 drop-ins under /usr/. Files in /etc/ are reserved for the local
43 administrator, who may use this logic to override the configuration
44 files installed by vendor packages. Drop-ins have to be used to
45 override package drop-ins, since the main configuration file has lower
46 precedence. It is recommended to prefix all filenames in those
47 subdirectories with a two-digit number and a dash, to simplify the
48 ordering of the files.
49 To disable a configuration file supplied by the vendor, the recommended
51 way is to place a symlink to /dev/null in the configuration directory
52 in /etc/, with the same filename as the vendor configuration file.
53
55 The following options are available in the [OOM] section:
56 SwapUsedLimit=
58 Sets the limit for memory and swap usage on the system before
59 systemd-oomd will take action. If the fraction of memory used and
60 the fraction of swap used on the system are both more than what is
61 defined here, systemd-oomd will act on eligible descendant control
62 groups with swap usage greater than 5% of total swap, starting from
63 the ones with the highest swap usage. Which control groups are
64 monitored and what action gets taken depends on what the unit has
65 configured for ManagedOOMSwap=. Takes a value specified in percent
66 (when suffixed with "%"), permille ("‰") or permyriad ("‱"),
67 between 0% and 100%, inclusive. Defaults to 90%.
68 DefaultMemoryPressureLimit=
70 Sets the limit for memory pressure on the unit's control group
71 before systemd-oomd will take action. A unit can override this
72 value with ManagedOOMMemoryPressureLimit=. The memory pressure for
73 this property represents the fraction of time in a 10 second window
74 in which all tasks in the control group were delayed. For each
75 monitored control group, if the memory pressure on that control
76 group exceeds the limit set for longer than the duration set by
77 DefaultMemoryPressureDurationSec=, systemd-oomd will act on
78 eligible descendant control groups, starting from the ones with the
79 most reclaim activity to the least reclaim activity. Which control
80 groups are monitored and what action gets taken depends on what the
81 unit has configured for ManagedOOMMemoryPressure=. Takes a fraction
82 specified in the same way as SwapUsedLimit= above. Defaults to 60%.
83 DefaultMemoryPressureDurationSec=
85 Sets the amount of time a unit's control group needs to have
86 exceeded memory pressure limits before systemd-oomd will take
87 action. Memory pressure limits are defined by
88 DefaultMemoryPressureLimit= and ManagedOOMMemoryPressureLimit=.
89 Must be set to 0, or at least 1 second. Defaults to 30 seconds when
90 unset or 0.
91
93 systemd(1), systemd.resource-control(5), systemd-oomd.service(8),
94 oomctl(1)
95systemd 250 OOMD.CONF(5)