catalog: add more entries

While message IDs are about more than catalog entries (they make
messages recognizable), I think it makes sense to document at least all
those messages that indicate problems with catalog entries, in an
attempt to be helpful to users.

Fixes: #36201

diff --git a/catalog/systemd.catalog.in b/catalog/systemd.catalog.in
index 610b6f5fabe087725b23901b5e27a7c2ac9bd432..5b22b3b7ffe93a358d0b5281fa608e6c4718b70f 100644 (file)
--- a/catalog/systemd.catalog.in
+++ b/catalog/systemd.catalog.in
@@ -834,3 +834,83 @@ interactively requesting confirmation by the user.
 Clearing the TPM has the effect of invalidating all keys locked to the TPM,
 including full disk encryption keys. Because of that care should be taken that
 access to relevant resources is retained via other means.
+
+-- 1f4e0a44a88649939aaea34fc6da8c95
+Subject: Process @COREDUMP_PID@ (@COREDUMP_COMM@) terminated abnormally
+Defined-By: systemd
+Support: %SUPPORT_URL%
+Documentation: man:systemd-coredump(8)
+
+Process @COREDUMP_PID@ (@COREDUMP_COMM@) terminated abnormally and generated a
+stack trace.
+
+This usually indicates a programming error in the crashing program and should
+be reported to its vendor as a bug. A program stack trace is available that
+indicates where the issue was encountered, which may be used to track down the
+problem.
+
+-- d989611b15e44c9dbf31e3c81256e4ed
+Subject: systemd-oomd killed one or more processes in unit @UNIT@
+Defined-By: systemd
+Support: %SUPPORT_URL%
+Documentation: man:systemd-oomd.service(8)
+
+One or more processes in the @UNIT@ unit have been killed by systemd-oomd, in
+order to counter an out-of-memory situation on the system. This usually
+indicates that the system is low on memory and systemd-oomd decided to
+terminate one or more processes to reduce memory pressure.
+
+Note that the memory pressure might or might not have been caused by @UNIT@.
+
+-- 010190138f494e29a0ef6669749531aa
+Subject: No valid unit name can be generated for device @DEVICE@
+Defined-By: systemd
+Support: %SUPPORT_URL%
+Documentation: man:systemd(1)
+
+A kernel device @DEVICE@ has been encountered whose identification cannot be
+turned into a valid systemd unit name. This typically indicates a problematic
+device hierarchy (i.e. too deep nesting of buses) or drivers.
+
+For devices like this no .device unit will be created that follows the
+underlying kernel device's state, and hence no dependencies on such a unit can
+be fulfilled.
+
+-- 7db73c8af0d94eeb822ae04323fe6ab6
+Subject: The system clock has been changed
+Defined-By: systemd
+Support: %SUPPORT_URL%
+Documentation: man:systemd(1) man:systemd-timesyncd.service(8)
+
+The system clock has been moved @DIRECTION@, the new time is
+@REALTIME_USEC@ microseconds after the epoch.
+
+Typically, this should only happen on major misconfiguration of the system
+clock or when the system lacks a battery-buffered hardware clock (or the
+battery has expired).
+
+-- 8739789eca064325af15a8ed0ecfc556
+Subject: Sending a keep-alive to the hardware watchdog device failed
+Defined-By: systemd
+Support: %SUPPORT_URL%
+Documentation: man:systemd(1)
+
+An error occurred while sending a keep-alive message to the hardware watchdog
+device @WATCHDOG_DEVICE@. This usually indicates driver or hardware problems.
+
+Failure to issue keep-alive messages regularly to the watchdog hardware might
+result in automatic reboots of the system.
+
+-- 375ac151ef9d4de39068b3efbfed0cee
+Subject: Opening of the configure watchdog device failed
+Defined-By: systemd
+Support: %SUPPORT_URL%
+Documentation: man:systemd(1)
+
+An error occurred while opening the hardware watchdog device
+@WATCHDOG_DEVICE@. This usually indicates invalid configuration
+(i.e. configuration not matching the local system), or driver or hardware
+problems.
+
+If watchdog support is configured, but the watchdog hardware cannot be opened
+the system will not be protected by the watchdog logic.