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 -- fc2e22bc6ee647b6b90729ab34a250b1 de
  92 Subject: Speicherabbild für Prozess @COREDUMP_PID@ (@COREDUMP_COMM) generiert
  93 Defined-By: systemd
  94 Support: %SUPPORT_URL%
  95 Documentation: man:core(5)
  96
  97 Prozess @COREDUMP_PID@ (@COREDUMP_COMM@) ist abgebrochen worden und
  98 ein Speicherabbild wurde generiert.
  99
 100 Üblicherweise ist dies ein Hinweis auf einen Programmfehler und sollte
 101 als Fehler dem jeweiligen Hersteller gemeldet werden.
 102
 103 -- 8d45620c1a4348dbb17410da57c60c66
 104 Subject: A new session @SESSION_ID@ has been created for user @USER_ID@
 105 Defined-By: systemd
 106 Support: %SUPPORT_URL%
 107 Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
 108
 109 A new session with the ID @SESSION_ID@ has been created for the user @USER_ID@.
 110
 111 The leading process of the session is @LEADER@.
 112
 113 -- 3354939424b4456d9802ca8333ed424a
 114 Subject: Session @SESSION_ID@ has been terminated
 115 Defined-By: systemd
 116 Support: %SUPPORT_URL%
 117 Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
 118
 119 A session with the ID @SESSION_ID@ has been terminated.
 120
 121 -- fcbefc5da23d428093f97c82a9290f7b
 122 Subject: A new seat @SEAT_ID@ is now available
 123 Defined-By: systemd
 124 Support: %SUPPORT_URL%
 125 Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
 126
 127 A new seat @SEAT_ID@ has been configured and is now available.
 128
 129 -- e7852bfe46784ed0accde04bc864c2d5
 130 Subject: Seat @SEAT_ID@ has now been removed
 131 Defined-By: systemd
 132 Support: %SUPPORT_URL%
 133 Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
 134
 135 A seat @SEAT_ID@ has been removed and is no longer available.
 136
 137 -- c7a787079b354eaaa9e77b371893cd27
 138 Subject: Time change
 139 Defined-By: systemd
 140 Support: %SUPPORT_URL%
 141
 142 The system clock has been changed to @REALTIME@ microseconds after January 1st, 1970.
 143
 144 -- c7a787079b354eaaa9e77b371893cd27 de
 145 Subject: Zeitänderung
 146 Defined-By: systemd
 147 Support: %SUPPORT_URL%
 148
 149 Die System-Zeit wurde geändert auf @REALTIME@ Mikrosekunden nach dem 1. Januar 1970.
 150
 151 -- 45f82f4aef7a4bbf942ce861d1f20990
 152 Subject: Time zone change to @TIMEZONE@
 153 Defined-By: systemd
 154 Support: %SUPPORT_URL%
 155
 156 The system timezone has been changed to @TIMEZONE@.
 157
 158 -- b07a249cd024414a82dd00cd181378ff
 159 Subject: System start-up is now complete
 160 Defined-By: systemd
 161 Support: %SUPPORT_URL%
 162
 163 All system services necessary queued for starting at boot have been
 164 successfully started. Note that this does not mean that the machine is
 165 now idle as services might still be busy with completing start-up.
 166
 167 Kernel start-up required @KERNEL_USEC@ microseconds.
 168
 169 Initial RAM disk start-up required @INITRD_USEC@ microseconds.
 170
 171 Userspace start-up required @USERSPACE_USEC@ microseconds.
 172
 173 -- 6bbd95ee977941e497c48be27c254128
 174 Subject: System sleep state @SLEEP@ entered
 175 Defined-By: systemd
 176 Support: %SUPPORT_URL%
 177
 178 The system has now entered the @SLEEP@ sleep state.
 179
 180 -- 8811e6df2a8e40f58a94cea26f8ebf14
 181 Subject: System sleep state @SLEEP@ left
 182 Defined-By: systemd
 183 Support: %SUPPORT_URL%
 184
 185 The system has now left the @SLEEP@ sleep state.
 186
 187 -- 98268866d1d54a499c4e98921d93bc40
 188 Subject: System shutdown initiated
 189 Defined-By: systemd
 190 Support: %SUPPORT_URL%
 191
 192 Systemd shutdown has been initiated. The shutdown has now begun and
 193 all system services are terminated and all file systems unmounted.
 194
 195 -- 7d4958e842da4a758f6c1cdc7b36dcc5
 196 Subject: Unit @UNIT@ has begun start-up
 197 Defined-By: systemd
 198 Support: %SUPPORT_URL%
 199
 200 Unit @UNIT@ has begun starting up.
 201
 202 -- 39f53479d3a045ac8e11786248231fbf
 203 Subject: Unit @UNIT@ has finished start-up
 204 Defined-By: systemd
 205 Support: %SUPPORT_URL%
 206
 207 Unit @UNIT@ has finished starting up.
 208
 209 The start-up result is @RESULT@.
 210
 211 -- de5b426a63be47a7b6ac3eaac82e2f6f
 212 Subject: Unit @UNIT@ has begun shutting down
 213 Defined-By: systemd
 214 Support: %SUPPORT_URL%
 215
 216 Unit @UNIT@ has begun shutting down.
 217
 218 -- 9d1aaa27d60140bd96365438aad20286
 219 Subject: Unit @UNIT@ has finished shutting down
 220 Defined-By: systemd
 221 Support: %SUPPORT_URL%
 222
 223 Unit @UNIT@ has finished shutting down.
 224
 225 -- be02cf6855d2428ba40df7e9d022f03d
 226 Subject: Unit @UNIT@ has failed
 227 Defined-By: systemd
 228 Support: %SUPPORT_URL%
 229
 230 Unit @UNIT@ has failed.
 231
 232 The result is @RESULT@.
 233
 234 -- d34d037fff1847e6ae669a370e694725
 235 Subject: Unit @UNIT@ has begun reloading its configuration
 236 Defined-By: systemd
 237 Support: %SUPPORT_URL%
 238
 239 Unit @UNIT@ has begun reloading its configuration
 240
 241 -- 7b05ebc668384222baa8881179cfda54
 242 Subject: Unit @UNIT@ has finished reloading its configuration
 243 Defined-By: systemd
 244 Support: %SUPPORT_URL%
 245
 246 Unit @UNIT@ has finished reloading its configuration
 247
 248 The result is @RESULT@.
 249
 250 -- 641257651c1b4ec9a8624d7a40a9e1e7
 251 Subject: Process @EXECUTABLE@ could not be executed
 252 Defined-By: systemd
 253 Support: %SUPPORT_URL%
 254
 255 The process @EXECUTABLE@ could not be executed and failed.
 256
 257 The error number returned by this process is @ERRNO@.
 258
 259 -- 0027229ca0644181a76c4e92458afa2e
 260 Subject: One or more messages could not be forwarded to syslog
 261 Defined-By: systemd
 262 Support: %SUPPORT_URL%
 263
 264 One or more messages could not be forwarded to the syslog service
 265 running side-by-side with journald. This usually indicates that the
 266 syslog implementation has not been able to keep up with the speed of
 267 messages queued.
 268
 269 -- 1dee0369c7fc4736b7099b38ecb46ee7
 270 Subject: Mount point is not empty
 271 Defined-By: systemd
 272 Support: %SUPPORT_URL%
 273
 274 The directory @WHERE@ is specified as the mount point (second field in
 275 /etc/fstab or Where= field in systemd unit file) and is not empty.
 276 This does not interfere with mounting, but the pre-exisiting files in
 277 this directory become inaccessible. To see those over-mounted files,
 278 please manually mount the underlying file system to a secondary
 279 location.
 280
 281 -- 24d8d4452573402496068381a6312df2
 282 Subject: A virtual machine or container has been started
 283 Defined-By: systemd
 284 Support: %SUPPORT_URL%
 285
 286 The virtual machine @NAME@ with its leader PID @LEADER@ has been
 287 started is now ready to use.
 288
 289 -- 58432bd3bace477cb514b56381b8a758
 290 Subject: A virtual machine or container has been terminated
 291 Defined-By: systemd
 292 Support: %SUPPORT_URL%
 293
 294 The virtual machine @NAME@ with its leader PID @LEADER@ has been
 295 shut down.
 296
 297 -- 36db2dfa5a9045e1bd4af5f93e1cf057
 298 Subject: DNSSEC mode has been turned off, as server doesn't support it
 299 Defined-By: systemd
 300 Support: %SUPPORT_URL%
 301 Documentation: man:systemd-resolved.service(8) resolved.conf(5)
 302
 303 The resolver service (systemd-resolved.service) has detected that the
 304 configured DNS server does not support DNSSEC, and DNSSEC validation has been
 305 turned off as result.
 306
 307 This event will take place if DNSSEC=allow-downgrade is configured in
 308 resolved.conf and the configured DNS server is incompatible with DNSSEC. Note
 309 that using this mode permits DNSSEC downgrade attacks, as an attacker might be
 310 able turn off DNSSEC validation on the system by inserting DNS replies in the
 311 communication channel that result in a downgrade like this.
 312
 313 This event might be indication that the DNS server is indeed incompatible with
 314 DNSSEC or that an attacker has successfully managed to stage such a downgrade
 315 attack.
 316
 317 -- 1675d7f172174098b1108bf8c7dc8f5d
 318 Subject: DNSSEC validation failed
 319 Defined-By: systemd
 320 Support: %SUPPORT_URL%
 321 Documentation: man:systemd-resolved.service(8)
 322
 323 A DNS query or resource record set failed DNSSEC validation. This is usually
 324 indication that the communication channel used was tampered with.
 325
 326 -- 4d4408cfd0d144859184d1e65d7c8a65
 327 Subject: A DNSSEC trust anchor has been revoked
 328 Defined-By: systemd
 329 Support: %SUPPORT_URL%
 330 Documentation: man:systemd-resolved.service(8)
 331
 332 A DNSSEC trust anchor has been revoked. A new trust anchor has to be
 333 configured, or the operating system needs to be updated, to provide an updated
 334 DNSSEC trust anchor.