1 # This file is part of systemd.
3 # Copyright 2012 Lennart Poettering
5 # systemd is free software; you can redistribute it and/or modify it
6 # under the terms of the GNU Lesser General Public License as published by
7 # the Free Software Foundation; either version 2.1 of the License, or
8 # (at your option) any later version.
10 # systemd is distributed in the hope that it will be useful, but
11 # WITHOUT ANY WARRANTY; without even the implied warranty of
12 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
13 # Lesser General Public License for more details.
15 # You should have received a copy of the GNU Lesser General Public License
16 # along with systemd; If not, see <http://www.gnu.org/licenses/>.
18 # Message catalog for systemd's own messages
20 # The catalog format is documented on
21 # https://www.freedesktop.org/wiki/Software/systemd/catalog
23 # For an explanation why we do all this, see https://xkcd.com/1024/
25 -- f77379a8490b408bbe5f6940505a777b
26 Subject: The journal has been started
28 Support: %SUPPORT_URL%
30 The system journal process has started up, opened the journal
31 files for writing and is now ready to process requests.
33 -- d93fb3c9c24d451a97cea615ce59c00b
34 Subject: The journal has been stopped
36 Support: %SUPPORT_URL%
38 The system journal process has shut down and closed all currently
41 -- ec387f577b844b8fa948f33cad9a75e6
42 Subject: Disk space used by the journal
44 Support: %SUPPORT_URL%
46 @JOURNAL_NAME@ (@JOURNAL_PATH@) is currently using @CURRENT_USE_PRETTY@.
47 Maximum allowed usage is set to @MAX_USE_PRETTY@.
48 Leaving at least @DISK_KEEP_FREE_PRETTY@ free (of currently available @DISK_AVAILABLE_PRETTY@ of disk space).
49 Enforced usage limit is thus @LIMIT_PRETTY@, of which @AVAILABLE_PRETTY@ are still available.
51 The limits controlling how much disk space is used by the journal may
52 be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
53 RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
54 /etc/systemd/journald.conf. See journald.conf(5) for details.
56 -- a596d6fe7bfa4994828e72309e95d61e
57 Subject: Messages from a service have been suppressed
59 Support: %SUPPORT_URL%
60 Documentation: man:journald.conf(5)
62 A service has logged too many messages within a time period. Messages
63 from the service have been dropped.
65 Note that only messages from the service in question have been
66 dropped, other services' messages are unaffected.
68 The limits controlling when messages are dropped may be configured
69 with RateLimitIntervalSec= and RateLimitBurst= in
70 /etc/systemd/journald.conf. See journald.conf(5) for details.
72 -- e9bf28e6e834481bb6f48f548ad13606
73 Subject: Journal messages have been missed
75 Support: %SUPPORT_URL%
77 Kernel messages have been lost as the journal system has been unable
78 to process them quickly enough.
80 -- fc2e22bc6ee647b6b90729ab34a250b1
81 Subject: Process @COREDUMP_PID@ (@COREDUMP_COMM@) dumped core
83 Support: %SUPPORT_URL%
84 Documentation: man:core(5)
86 Process @COREDUMP_PID@ (@COREDUMP_COMM@) crashed and dumped core.
88 This usually indicates a programming error in the crashing program and
89 should be reported to its vendor as a bug.
91 -- 5aadd8e954dc4b1a8c954d63fd9e1137
92 Subject: Core file was truncated to @SIZE_LIMIT@ bytes.
94 Support: %SUPPORT_URL%
95 Documentation: man:coredump.conf(5)
97 The process had more memory mapped than the configured maximum for processing
98 and storage by systemd-coredump(8). Only the first @SIZE_LIMIT@ bytes were
99 saved. This core might still be usable, but various tools like gdb(1) will warn
100 about the file being truncated.
102 -- 8d45620c1a4348dbb17410da57c60c66
103 Subject: A new session @SESSION_ID@ has been created for user @USER_ID@
105 Support: %SUPPORT_URL%
106 Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
108 A new session with the ID @SESSION_ID@ has been created for the user @USER_ID@.
110 The leading process of the session is @LEADER@.
112 -- 3354939424b4456d9802ca8333ed424a
113 Subject: Session @SESSION_ID@ has been terminated
115 Support: %SUPPORT_URL%
116 Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
118 A session with the ID @SESSION_ID@ has been terminated.
120 -- fcbefc5da23d428093f97c82a9290f7b
121 Subject: A new seat @SEAT_ID@ is now available
123 Support: %SUPPORT_URL%
124 Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
126 A new seat @SEAT_ID@ has been configured and is now available.
128 -- e7852bfe46784ed0accde04bc864c2d5
129 Subject: Seat @SEAT_ID@ has now been removed
131 Support: %SUPPORT_URL%
132 Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
134 A seat @SEAT_ID@ has been removed and is no longer available.
136 -- c7a787079b354eaaa9e77b371893cd27
139 Support: %SUPPORT_URL%
141 The system clock has been changed to @REALTIME@ microseconds after January 1st, 1970.
143 -- c7a787079b354eaaa9e77b371893cd27 de
144 Subject: Zeitänderung
146 Support: %SUPPORT_URL%
148 Die System-Zeit wurde geändert auf @REALTIME@ Mikrosekunden nach dem 1. Januar 1970.
150 -- 45f82f4aef7a4bbf942ce861d1f20990
151 Subject: Time zone change to @TIMEZONE@
153 Support: %SUPPORT_URL%
155 The system timezone has been changed to @TIMEZONE@.
157 -- b07a249cd024414a82dd00cd181378ff
158 Subject: System start-up is now complete
160 Support: %SUPPORT_URL%
162 All system services necessary queued for starting at boot have been
163 started. Note that this does not mean that the machine is now idle as services
164 might still be busy with completing start-up.
166 Kernel start-up required @KERNEL_USEC@ microseconds.
168 Initial RAM disk start-up required @INITRD_USEC@ microseconds.
170 Userspace start-up required @USERSPACE_USEC@ microseconds.
172 -- eed00a68ffd84e31882105fd973abdd1
173 Subject: User manager start-up is now complete
175 Support: %SUPPORT_URL%
177 The user manager instance for user @_UID@ has been started. All services queued
178 for starting have been started. Note that other services might still be starting
179 up or be started at any later time.
181 Startup of the manager took @USERSPACE_USEC@ microseconds.
183 -- 6bbd95ee977941e497c48be27c254128
184 Subject: System sleep state @SLEEP@ entered
186 Support: %SUPPORT_URL%
188 The system has now entered the @SLEEP@ sleep state.
190 -- 8811e6df2a8e40f58a94cea26f8ebf14
191 Subject: System sleep state @SLEEP@ left
193 Support: %SUPPORT_URL%
195 The system has now left the @SLEEP@ sleep state.
197 -- 98268866d1d54a499c4e98921d93bc40
198 Subject: System shutdown initiated
200 Support: %SUPPORT_URL%
202 Systemd shutdown has been initiated. The shutdown has now begun and
203 all system services are terminated and all file systems unmounted.
205 -- 7d4958e842da4a758f6c1cdc7b36dcc5
206 Subject: Unit @UNIT@ has begun start-up
208 Support: %SUPPORT_URL%
210 Unit @UNIT@ has begun starting up.
212 -- 39f53479d3a045ac8e11786248231fbf
213 Subject: Unit @UNIT@ has finished start-up
215 Support: %SUPPORT_URL%
217 Unit @UNIT@ has finished starting up.
219 The start-up result is @RESULT@.
221 -- de5b426a63be47a7b6ac3eaac82e2f6f
222 Subject: Unit @UNIT@ has begun shutting down
224 Support: %SUPPORT_URL%
226 Unit @UNIT@ has begun shutting down.
228 -- 9d1aaa27d60140bd96365438aad20286
229 Subject: Unit @UNIT@ has finished shutting down
231 Support: %SUPPORT_URL%
233 Unit @UNIT@ has finished shutting down.
235 -- be02cf6855d2428ba40df7e9d022f03d
236 Subject: Unit @UNIT@ has failed
238 Support: %SUPPORT_URL%
240 Unit @UNIT@ has failed.
242 The result is @RESULT@.
244 -- d34d037fff1847e6ae669a370e694725
245 Subject: Unit @UNIT@ has begun reloading its configuration
247 Support: %SUPPORT_URL%
249 Unit @UNIT@ has begun reloading its configuration
251 -- 7b05ebc668384222baa8881179cfda54
252 Subject: Unit @UNIT@ has finished reloading its configuration
254 Support: %SUPPORT_URL%
256 Unit @UNIT@ has finished reloading its configuration
258 The result is @RESULT@.
260 -- 641257651c1b4ec9a8624d7a40a9e1e7
261 Subject: Process @EXECUTABLE@ could not be executed
263 Support: %SUPPORT_URL%
265 The process @EXECUTABLE@ could not be executed and failed.
267 The error number returned by this process is @ERRNO@.
269 -- 0027229ca0644181a76c4e92458afa2e
270 Subject: One or more messages could not be forwarded to syslog
272 Support: %SUPPORT_URL%
274 One or more messages could not be forwarded to the syslog service
275 running side-by-side with journald. This usually indicates that the
276 syslog implementation has not been able to keep up with the speed of
279 -- 1dee0369c7fc4736b7099b38ecb46ee7
280 Subject: Mount point is not empty
282 Support: %SUPPORT_URL%
284 The directory @WHERE@ is specified as the mount point (second field in
285 /etc/fstab or Where= field in systemd unit file) and is not empty.
286 This does not interfere with mounting, but the pre-exisiting files in
287 this directory become inaccessible. To see those over-mounted files,
288 please manually mount the underlying file system to a secondary
291 -- 24d8d4452573402496068381a6312df2
292 Subject: A virtual machine or container has been started
294 Support: %SUPPORT_URL%
296 The virtual machine @NAME@ with its leader PID @LEADER@ has been
297 started is now ready to use.
299 -- 58432bd3bace477cb514b56381b8a758
300 Subject: A virtual machine or container has been terminated
302 Support: %SUPPORT_URL%
304 The virtual machine @NAME@ with its leader PID @LEADER@ has been
307 -- 36db2dfa5a9045e1bd4af5f93e1cf057
308 Subject: DNSSEC mode has been turned off, as server doesn't support it
310 Support: %SUPPORT_URL%
311 Documentation: man:systemd-resolved.service(8) resolved.conf(5)
313 The resolver service (systemd-resolved.service) has detected that the
314 configured DNS server does not support DNSSEC, and DNSSEC validation has been
315 turned off as result.
317 This event will take place if DNSSEC=allow-downgrade is configured in
318 resolved.conf and the configured DNS server is incompatible with DNSSEC. Note
319 that using this mode permits DNSSEC downgrade attacks, as an attacker might be
320 able turn off DNSSEC validation on the system by inserting DNS replies in the
321 communication channel that result in a downgrade like this.
323 This event might be indication that the DNS server is indeed incompatible with
324 DNSSEC or that an attacker has successfully managed to stage such a downgrade
327 -- 1675d7f172174098b1108bf8c7dc8f5d
328 Subject: DNSSEC validation failed
330 Support: %SUPPORT_URL%
331 Documentation: man:systemd-resolved.service(8)
333 A DNS query or resource record set failed DNSSEC validation. This is usually
334 indication that the communication channel used was tampered with.
336 -- 4d4408cfd0d144859184d1e65d7c8a65
337 Subject: A DNSSEC trust anchor has been revoked
339 Support: %SUPPORT_URL%
340 Documentation: man:systemd-resolved.service(8)
342 A DNSSEC trust anchor has been revoked. A new trust anchor has to be
343 configured, or the operating system needs to be updated, to provide an updated
346 -- 5eb03494b6584870a536b337290809b3
347 Subject: Automatic restarting of a unit has been scheduled
349 Support: %SUPPORT_URL%
351 Automatic restarting of the unit @UNIT@ has been scheduled, as the result for
352 the configured Restart= setting for the unit.
354 -- ae8f7b866b0347b9af31fe1c80b127c0
355 Subject: Resources consumed by unit runtime
357 Support: %SUPPORT_URL%
359 The unit @UNIT@ completed and consumed the indicated resources.