catalog/systemd.catalog.in

   1 #  This file is part of systemd.
   2 #
   3 #  Copyright 2012 Lennart Poettering
   4 #
   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.
   9 #
  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.
  14 #
  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/>.
  17
  18 # Message catalog for systemd's own messages
  19
  20 # The catalog format is documented on
  21 # http://www.freedesktop.org/wiki/Software/systemd/catalog
  22
  23 # For an explanation why we do all this, see https://xkcd.com/1024/
  24
  25 -- f77379a8490b408bbe5f6940505a777b
  26 Subject: The journal has been started
  27 Defined-By: systemd
  28 Support: %SUPPORT_URL%
  29
  30 The system journal process has started up, opened the journal
  31 files for writing and is now ready to process requests.
  32
  33 -- d93fb3c9c24d451a97cea615ce59c00b
  34 Subject: The journal has been stopped
  35 Defined-By: systemd
  36 Support: %SUPPORT_URL%
  37
  38 The system journal process has shut down and closed all currently
  39 active journal files.
  40
  41 -- ec387f577b844b8fa948f33cad9a75e6
  42 Subject: Disk space used by the journal
  43 Defined-By: systemd
  44 Support: %SUPPORT_URL%
  45
  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.
  50
  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.
  55
  56 -- a596d6fe7bfa4994828e72309e95d61e
  57 Subject: Messages from a service have been suppressed
  58 Defined-By: systemd
  59 Support: %SUPPORT_URL%
  60 Documentation: man:journald.conf(5)
  61
  62 A service has logged too many messages within a time period. Messages
  63 from the service have been dropped.
  64
  65 Note that only messages from the service in question have been
  66 dropped, other services' messages are unaffected.
  67
  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.
  71
  72 -- e9bf28e6e834481bb6f48f548ad13606
  73 Subject: Journal messages have been missed
  74 Defined-By: systemd
  75 Support: %SUPPORT_URL%
  76
  77 Kernel messages have been lost as the journal system has been unable
  78 to process them quickly enough.
  79
  80 -- fc2e22bc6ee647b6b90729ab34a250b1
  81 Subject: Process @COREDUMP_PID@ (@COREDUMP_COMM@) dumped core
  82 Defined-By: systemd
  83 Support: %SUPPORT_URL%
  84 Documentation: man:core(5)
  85
  86 Process @COREDUMP_PID@ (@COREDUMP_COMM@) crashed and dumped core.
  87
  88 This usually indicates a programming error in the crashing program and
  89 should be reported to its vendor as a bug.
  90
  91 -- 5aadd8e954dc4b1a8c954d63fd9e1137
  92 Subject: Core file was truncated to @SIZE_LIMIT@ bytes.
  93 Defined-By: systemd
  94 Support: %SUPPORT_URL%
  95 Documentation: man:coredump.conf(5)
  96
  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.
 101
 102 -- fc2e22bc6ee647b6b90729ab34a250b1 de
 103 Subject: Speicherabbild für Prozess @COREDUMP_PID@ (@COREDUMP_COMM) generiert
 104 Defined-By: systemd
 105 Support: %SUPPORT_URL%
 106 Documentation: man:core(5)
 107
 108 Prozess @COREDUMP_PID@ (@COREDUMP_COMM@) ist abgebrochen worden und
 109 ein Speicherabbild wurde generiert.
 110
 111 Üblicherweise ist dies ein Hinweis auf einen Programmfehler und sollte
 112 als Fehler dem jeweiligen Hersteller gemeldet werden.
 113
 114 -- 8d45620c1a4348dbb17410da57c60c66
 115 Subject: A new session @SESSION_ID@ has been created for user @USER_ID@
 116 Defined-By: systemd
 117 Support: %SUPPORT_URL%
 118 Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
 119
 120 A new session with the ID @SESSION_ID@ has been created for the user @USER_ID@.
 121
 122 The leading process of the session is @LEADER@.
 123
 124 -- 3354939424b4456d9802ca8333ed424a
 125 Subject: Session @SESSION_ID@ has been terminated
 126 Defined-By: systemd
 127 Support: %SUPPORT_URL%
 128 Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
 129
 130 A session with the ID @SESSION_ID@ has been terminated.
 131
 132 -- fcbefc5da23d428093f97c82a9290f7b
 133 Subject: A new seat @SEAT_ID@ is now available
 134 Defined-By: systemd
 135 Support: %SUPPORT_URL%
 136 Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
 137
 138 A new seat @SEAT_ID@ has been configured and is now available.
 139
 140 -- e7852bfe46784ed0accde04bc864c2d5
 141 Subject: Seat @SEAT_ID@ has now been removed
 142 Defined-By: systemd
 143 Support: %SUPPORT_URL%
 144 Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
 145
 146 A seat @SEAT_ID@ has been removed and is no longer available.
 147
 148 -- c7a787079b354eaaa9e77b371893cd27
 149 Subject: Time change
 150 Defined-By: systemd
 151 Support: %SUPPORT_URL%
 152
 153 The system clock has been changed to @REALTIME@ microseconds after January 1st, 1970.
 154
 155 -- c7a787079b354eaaa9e77b371893cd27 de
 156 Subject: Zeitänderung
 157 Defined-By: systemd
 158 Support: %SUPPORT_URL%
 159
 160 Die System-Zeit wurde geändert auf @REALTIME@ Mikrosekunden nach dem 1. Januar 1970.
 161
 162 -- 45f82f4aef7a4bbf942ce861d1f20990
 163 Subject: Time zone change to @TIMEZONE@
 164 Defined-By: systemd
 165 Support: %SUPPORT_URL%
 166
 167 The system timezone has been changed to @TIMEZONE@.
 168
 169 -- b07a249cd024414a82dd00cd181378ff
 170 Subject: System start-up is now complete
 171 Defined-By: systemd
 172 Support: %SUPPORT_URL%
 173
 174 All system services necessary queued for starting at boot have been
 175 successfully started. Note that this does not mean that the machine is
 176 now idle as services might still be busy with completing start-up.
 177
 178 Kernel start-up required @KERNEL_USEC@ microseconds.
 179
 180 Initial RAM disk start-up required @INITRD_USEC@ microseconds.
 181
 182 Userspace start-up required @USERSPACE_USEC@ microseconds.
 183
 184 -- 6bbd95ee977941e497c48be27c254128
 185 Subject: System sleep state @SLEEP@ entered
 186 Defined-By: systemd
 187 Support: %SUPPORT_URL%
 188
 189 The system has now entered the @SLEEP@ sleep state.
 190
 191 -- 8811e6df2a8e40f58a94cea26f8ebf14
 192 Subject: System sleep state @SLEEP@ left
 193 Defined-By: systemd
 194 Support: %SUPPORT_URL%
 195
 196 The system has now left the @SLEEP@ sleep state.
 197
 198 -- 98268866d1d54a499c4e98921d93bc40
 199 Subject: System shutdown initiated
 200 Defined-By: systemd
 201 Support: %SUPPORT_URL%
 202
 203 Systemd shutdown has been initiated. The shutdown has now begun and
 204 all system services are terminated and all file systems unmounted.
 205
 206 -- 7d4958e842da4a758f6c1cdc7b36dcc5
 207 Subject: Unit @UNIT@ has begun start-up
 208 Defined-By: systemd
 209 Support: %SUPPORT_URL%
 210
 211 Unit @UNIT@ has begun starting up.
 212
 213 -- 39f53479d3a045ac8e11786248231fbf
 214 Subject: Unit @UNIT@ has finished start-up
 215 Defined-By: systemd
 216 Support: %SUPPORT_URL%
 217
 218 Unit @UNIT@ has finished starting up.
 219
 220 The start-up result is @RESULT@.
 221
 222 -- de5b426a63be47a7b6ac3eaac82e2f6f
 223 Subject: Unit @UNIT@ has begun shutting down
 224 Defined-By: systemd
 225 Support: %SUPPORT_URL%
 226
 227 Unit @UNIT@ has begun shutting down.
 228
 229 -- 9d1aaa27d60140bd96365438aad20286
 230 Subject: Unit @UNIT@ has finished shutting down
 231 Defined-By: systemd
 232 Support: %SUPPORT_URL%
 233
 234 Unit @UNIT@ has finished shutting down.
 235
 236 -- be02cf6855d2428ba40df7e9d022f03d
 237 Subject: Unit @UNIT@ has failed
 238 Defined-By: systemd
 239 Support: %SUPPORT_URL%
 240
 241 Unit @UNIT@ has failed.
 242
 243 The result is @RESULT@.
 244
 245 -- d34d037fff1847e6ae669a370e694725
 246 Subject: Unit @UNIT@ has begun reloading its configuration
 247 Defined-By: systemd
 248 Support: %SUPPORT_URL%
 249
 250 Unit @UNIT@ has begun reloading its configuration
 251
 252 -- 7b05ebc668384222baa8881179cfda54
 253 Subject: Unit @UNIT@ has finished reloading its configuration
 254 Defined-By: systemd
 255 Support: %SUPPORT_URL%
 256
 257 Unit @UNIT@ has finished reloading its configuration
 258
 259 The result is @RESULT@.
 260
 261 -- 641257651c1b4ec9a8624d7a40a9e1e7
 262 Subject: Process @EXECUTABLE@ could not be executed
 263 Defined-By: systemd
 264 Support: %SUPPORT_URL%
 265
 266 The process @EXECUTABLE@ could not be executed and failed.
 267
 268 The error number returned by this process is @ERRNO@.
 269
 270 -- 0027229ca0644181a76c4e92458afa2e
 271 Subject: One or more messages could not be forwarded to syslog
 272 Defined-By: systemd
 273 Support: %SUPPORT_URL%
 274
 275 One or more messages could not be forwarded to the syslog service
 276 running side-by-side with journald. This usually indicates that the
 277 syslog implementation has not been able to keep up with the speed of
 278 messages queued.
 279
 280 -- 1dee0369c7fc4736b7099b38ecb46ee7
 281 Subject: Mount point is not empty
 282 Defined-By: systemd
 283 Support: %SUPPORT_URL%
 284
 285 The directory @WHERE@ is specified as the mount point (second field in
 286 /etc/fstab or Where= field in systemd unit file) and is not empty.
 287 This does not interfere with mounting, but the pre-exisiting files in
 288 this directory become inaccessible. To see those over-mounted files,
 289 please manually mount the underlying file system to a secondary
 290 location.
 291
 292 -- 24d8d4452573402496068381a6312df2
 293 Subject: A virtual machine or container has been started
 294 Defined-By: systemd
 295 Support: %SUPPORT_URL%
 296
 297 The virtual machine @NAME@ with its leader PID @LEADER@ has been
 298 started is now ready to use.
 299
 300 -- 58432bd3bace477cb514b56381b8a758
 301 Subject: A virtual machine or container has been terminated
 302 Defined-By: systemd
 303 Support: %SUPPORT_URL%
 304
 305 The virtual machine @NAME@ with its leader PID @LEADER@ has been
 306 shut down.
 307
 308 -- 36db2dfa5a9045e1bd4af5f93e1cf057
 309 Subject: DNSSEC mode has been turned off, as server doesn't support it
 310 Defined-By: systemd
 311 Support: %SUPPORT_URL%
 312 Documentation: man:systemd-resolved.service(8) resolved.conf(5)
 313
 314 The resolver service (systemd-resolved.service) has detected that the
 315 configured DNS server does not support DNSSEC, and DNSSEC validation has been
 316 turned off as result.
 317
 318 This event will take place if DNSSEC=allow-downgrade is configured in
 319 resolved.conf and the configured DNS server is incompatible with DNSSEC. Note
 320 that using this mode permits DNSSEC downgrade attacks, as an attacker might be
 321 able turn off DNSSEC validation on the system by inserting DNS replies in the
 322 communication channel that result in a downgrade like this.
 323
 324 This event might be indication that the DNS server is indeed incompatible with
 325 DNSSEC or that an attacker has successfully managed to stage such a downgrade
 326 attack.
 327
 328 -- 1675d7f172174098b1108bf8c7dc8f5d
 329 Subject: DNSSEC validation failed
 330 Defined-By: systemd
 331 Support: %SUPPORT_URL%
 332 Documentation: man:systemd-resolved.service(8)
 333
 334 A DNS query or resource record set failed DNSSEC validation. This is usually
 335 indication that the communication channel used was tampered with.
 336
 337 -- 4d4408cfd0d144859184d1e65d7c8a65
 338 Subject: A DNSSEC trust anchor has been revoked
 339 Defined-By: systemd
 340 Support: %SUPPORT_URL%
 341 Documentation: man:systemd-resolved.service(8)
 342
 343 A DNSSEC trust anchor has been revoked. A new trust anchor has to be
 344 configured, or the operating system needs to be updated, to provide an updated
 345 DNSSEC trust anchor.