summaryrefslogtreecommitdiffstats
path: root/catalog
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2019-03-19 19:14:53 +0100
committerLennart Poettering <lennart@poettering.net>2019-04-09 11:17:58 +0200
commit34e86947e96a5b0c23097c40856c8ccac3bbed43 (patch)
tree5962df1d0038d89c873eec30ffe6971a47279046 /catalog
parentcore: implement OOMPolicy= and watch cgroups for OOM killings (diff)
downloadsystemd-34e86947e96a5b0c23097c40856c8ccac3bbed43.tar.xz
systemd-34e86947e96a5b0c23097c40856c8ccac3bbed43.zip
catalog: add a new catalog entry explaining the new OOM killer event log msg
Diffstat (limited to 'catalog')
-rw-r--r--catalog/systemd.catalog.in13
1 files changed, 13 insertions, 0 deletions
diff --git a/catalog/systemd.catalog.in b/catalog/systemd.catalog.in
index 5c6799ee5d..d39a2251b0 100644
--- a/catalog/systemd.catalog.in
+++ b/catalog/systemd.catalog.in
@@ -391,3 +391,16 @@ The following "tags" are possible:
- "overflowgid-not-65534" — the kernel group ID used for "unknown" users (with
NFS or user namespaces) is not 65534
Current system is tagged as @TAINT@.
+
+-- fe6faa94e7774663a0da52717891d8ef
+Subject: A process of @UNIT@ unit has been killed by the OOM killer.
+Defined-By: systemd
+Support: %SUPPORT_URL%
+
+A process of unit @UNIT has been killed by the Linux kernel out-of-memory (OOM)
+killer logic. This usually indicates that the system is low on memory and that
+memory needed to be freed. A process associated with @UNIT@ has been determined
+as the best process to terminate and has been forcibly terminated by the
+kernel.
+
+Note that the memory pressure might or might not have been caused by @UNIT@.