catalog/systemd.catalog.in

   1 # SPDX-License-Identifier: LGPL-2.1+
   2 #
   3 #  This file is part of systemd.
   4 #
   5 #  Copyright 2012 Lennart Poettering
   6
   7 # Message catalog for systemd's own messages
   8
   9 # The catalog format is documented on
  10 # https://www.freedesktop.org/wiki/Software/systemd/catalog
  11
  12 # For an explanation why we do all this, see https://xkcd.com/1024/
  13
  14 -- f77379a8490b408bbe5f6940505a777b
  15 Subject: The journal has been started
  16 Defined-By: systemd
  17 Support: %SUPPORT_URL%
  18
  19 The system journal process has started up, opened the journal
  20 files for writing and is now ready to process requests.
  21
  22 -- d93fb3c9c24d451a97cea615ce59c00b
  23 Subject: The journal has been stopped
  24 Defined-By: systemd
  25 Support: %SUPPORT_URL%
  26
  27 The system journal process has shut down and closed all currently
  28 active journal files.
  29
  30 -- ec387f577b844b8fa948f33cad9a75e6
  31 Subject: Disk space used by the journal
  32 Defined-By: systemd
  33 Support: %SUPPORT_URL%
  34
  35 @JOURNAL_NAME@ (@JOURNAL_PATH@) is currently using @CURRENT_USE_PRETTY@.
  36 Maximum allowed usage is set to @MAX_USE_PRETTY@.
  37 Leaving at least @DISK_KEEP_FREE_PRETTY@ free (of currently available @DISK_AVAILABLE_PRETTY@ of disk space).
  38 Enforced usage limit is thus @LIMIT_PRETTY@, of which @AVAILABLE_PRETTY@ are still available.
  39
  40 The limits controlling how much disk space is used by the journal may
  41 be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
  42 RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
  43 /etc/systemd/journald.conf. See journald.conf(5) for details.
  44
  45 -- a596d6fe7bfa4994828e72309e95d61e
  46 Subject: Messages from a service have been suppressed
  47 Defined-By: systemd
  48 Support: %SUPPORT_URL%
  49 Documentation: man:journald.conf(5)
  50
  51 A service has logged too many messages within a time period. Messages
  52 from the service have been dropped.
  53
  54 Note that only messages from the service in question have been
  55 dropped, other services' messages are unaffected.
  56
  57 The limits controlling when messages are dropped may be configured
  58 with RateLimitIntervalSec= and RateLimitBurst= in
  59 /etc/systemd/journald.conf. See journald.conf(5) for details.
  60
  61 -- e9bf28e6e834481bb6f48f548ad13606
  62 Subject: Journal messages have been missed
  63 Defined-By: systemd
  64 Support: %SUPPORT_URL%
  65
  66 Kernel messages have been lost as the journal system has been unable
  67 to process them quickly enough.
  68
  69 -- fc2e22bc6ee647b6b90729ab34a250b1
  70 Subject: Process @COREDUMP_PID@ (@COREDUMP_COMM@) dumped core
  71 Defined-By: systemd
  72 Support: %SUPPORT_URL%
  73 Documentation: man:core(5)
  74
  75 Process @COREDUMP_PID@ (@COREDUMP_COMM@) crashed and dumped core.
  76
  77 This usually indicates a programming error in the crashing program and
  78 should be reported to its vendor as a bug.
  79
  80 -- 5aadd8e954dc4b1a8c954d63fd9e1137
  81 Subject: Core file was truncated to @SIZE_LIMIT@ bytes.
  82 Defined-By: systemd
  83 Support: %SUPPORT_URL%
  84 Documentation: man:coredump.conf(5)
  85
  86 The process had more memory mapped than the configured maximum for processing
  87 and storage by systemd-coredump(8). Only the first @SIZE_LIMIT@ bytes were
  88 saved. This core might still be usable, but various tools like gdb(1) will warn
  89 about the file being truncated.
  90
  91 -- 8d45620c1a4348dbb17410da57c60c66
  92 Subject: A new session @SESSION_ID@ has been created for user @USER_ID@
  93 Defined-By: systemd
  94 Support: %SUPPORT_URL%
  95 Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
  96
  97 A new session with the ID @SESSION_ID@ has been created for the user @USER_ID@.
  98
  99 The leading process of the session is @LEADER@.
 100
 101 -- 3354939424b4456d9802ca8333ed424a
 102 Subject: Session @SESSION_ID@ has been terminated
 103 Defined-By: systemd
 104 Support: %SUPPORT_URL%
 105 Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
 106
 107 A session with the ID @SESSION_ID@ has been terminated.
 108
 109 -- fcbefc5da23d428093f97c82a9290f7b
 110 Subject: A new seat @SEAT_ID@ is now available
 111 Defined-By: systemd
 112 Support: %SUPPORT_URL%
 113 Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
 114
 115 A new seat @SEAT_ID@ has been configured and is now available.
 116
 117 -- e7852bfe46784ed0accde04bc864c2d5
 118 Subject: Seat @SEAT_ID@ has now been removed
 119 Defined-By: systemd
 120 Support: %SUPPORT_URL%
 121 Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
 122
 123 A seat @SEAT_ID@ has been removed and is no longer available.
 124
 125 -- c7a787079b354eaaa9e77b371893cd27
 126 Subject: Time change
 127 Defined-By: systemd
 128 Support: %SUPPORT_URL%
 129
 130 The system clock has been changed to @REALTIME@ microseconds after January 1st, 1970.
 131
 132 -- c7a787079b354eaaa9e77b371893cd27 de
 133 Subject: Zeitänderung
 134 Defined-By: systemd
 135 Support: %SUPPORT_URL%
 136
 137 Die System-Zeit wurde geändert auf @REALTIME@ Mikrosekunden nach dem 1. Januar 1970.
 138
 139 -- 45f82f4aef7a4bbf942ce861d1f20990
 140 Subject: Time zone change to @TIMEZONE@
 141 Defined-By: systemd
 142 Support: %SUPPORT_URL%
 143
 144 The system timezone has been changed to @TIMEZONE@.
 145
 146 -- b07a249cd024414a82dd00cd181378ff
 147 Subject: System start-up is now complete
 148 Defined-By: systemd
 149 Support: %SUPPORT_URL%
 150
 151 All system services necessary queued for starting at boot have been
 152 started. Note that this does not mean that the machine is now idle as services
 153 might still be busy with completing start-up.
 154
 155 Kernel start-up required @KERNEL_USEC@ microseconds.
 156
 157 Initial RAM disk start-up required @INITRD_USEC@ microseconds.
 158
 159 Userspace start-up required @USERSPACE_USEC@ microseconds.
 160
 161 -- eed00a68ffd84e31882105fd973abdd1
 162 Subject: User manager start-up is now complete
 163 Defined-By: systemd
 164 Support: %SUPPORT_URL%
 165
 166 The user manager instance for user @_UID@ has been started. All services queued
 167 for starting have been started. Note that other services might still be starting
 168 up or be started at any later time.
 169
 170 Startup of the manager took @USERSPACE_USEC@ microseconds.
 171
 172 -- 6bbd95ee977941e497c48be27c254128
 173 Subject: System sleep state @SLEEP@ entered
 174 Defined-By: systemd
 175 Support: %SUPPORT_URL%
 176
 177 The system has now entered the @SLEEP@ sleep state.
 178
 179 -- 8811e6df2a8e40f58a94cea26f8ebf14
 180 Subject: System sleep state @SLEEP@ left
 181 Defined-By: systemd
 182 Support: %SUPPORT_URL%
 183
 184 The system has now left the @SLEEP@ sleep state.
 185
 186 -- 98268866d1d54a499c4e98921d93bc40
 187 Subject: System shutdown initiated
 188 Defined-By: systemd
 189 Support: %SUPPORT_URL%
 190
 191 System shutdown has been initiated. The shutdown has now begun and
 192 all system services are terminated and all file systems unmounted.
 193
 194 -- 7d4958e842da4a758f6c1cdc7b36dcc5
 195 Subject: Unit @UNIT@ has begun start-up
 196 Defined-By: systemd
 197 Support: %SUPPORT_URL%
 198
 199 Unit @UNIT@ has begun starting up.
 200
 201 -- 39f53479d3a045ac8e11786248231fbf
 202 Subject: Unit @UNIT@ has finished start-up
 203 Defined-By: systemd
 204 Support: %SUPPORT_URL%
 205
 206 Unit @UNIT@ has finished starting up.
 207
 208 The start-up result is @RESULT@.
 209
 210 -- de5b426a63be47a7b6ac3eaac82e2f6f
 211 Subject: Unit @UNIT@ has begun shutting down
 212 Defined-By: systemd
 213 Support: %SUPPORT_URL%
 214
 215 Unit @UNIT@ has begun shutting down.
 216
 217 -- 9d1aaa27d60140bd96365438aad20286
 218 Subject: Unit @UNIT@ has finished shutting down
 219 Defined-By: systemd
 220 Support: %SUPPORT_URL%
 221
 222 Unit @UNIT@ has finished shutting down.
 223
 224 -- be02cf6855d2428ba40df7e9d022f03d
 225 Subject: Unit @UNIT@ has failed
 226 Defined-By: systemd
 227 Support: %SUPPORT_URL%
 228
 229 Unit @UNIT@ has failed.
 230
 231 The result is @RESULT@.
 232
 233 -- d34d037fff1847e6ae669a370e694725
 234 Subject: Unit @UNIT@ has begun reloading its configuration
 235 Defined-By: systemd
 236 Support: %SUPPORT_URL%
 237
 238 Unit @UNIT@ has begun reloading its configuration
 239
 240 -- 7b05ebc668384222baa8881179cfda54
 241 Subject: Unit @UNIT@ has finished reloading its configuration
 242 Defined-By: systemd
 243 Support: %SUPPORT_URL%
 244
 245 Unit @UNIT@ has finished reloading its configuration
 246
 247 The result is @RESULT@.
 248
 249 -- 641257651c1b4ec9a8624d7a40a9e1e7
 250 Subject: Process @EXECUTABLE@ could not be executed
 251 Defined-By: systemd
 252 Support: %SUPPORT_URL%
 253
 254 The process @EXECUTABLE@ could not be executed and failed.
 255
 256 The error number returned by this process is @ERRNO@.
 257
 258 -- 0027229ca0644181a76c4e92458afa2e
 259 Subject: One or more messages could not be forwarded to syslog
 260 Defined-By: systemd
 261 Support: %SUPPORT_URL%
 262
 263 One or more messages could not be forwarded to the syslog service
 264 running side-by-side with journald. This usually indicates that the
 265 syslog implementation has not been able to keep up with the speed of
 266 messages queued.
 267
 268 -- 1dee0369c7fc4736b7099b38ecb46ee7
 269 Subject: Mount point is not empty
 270 Defined-By: systemd
 271 Support: %SUPPORT_URL%
 272
 273 The directory @WHERE@ is specified as the mount point (second field in
 274 /etc/fstab or Where= field in systemd unit file) and is not empty.
 275 This does not interfere with mounting, but the pre-exisiting files in
 276 this directory become inaccessible. To see those over-mounted files,
 277 please manually mount the underlying file system to a secondary
 278 location.
 279
 280 -- 24d8d4452573402496068381a6312df2
 281 Subject: A virtual machine or container has been started
 282 Defined-By: systemd
 283 Support: %SUPPORT_URL%
 284
 285 The virtual machine @NAME@ with its leader PID @LEADER@ has been
 286 started is now ready to use.
 287
 288 -- 58432bd3bace477cb514b56381b8a758
 289 Subject: A virtual machine or container has been terminated
 290 Defined-By: systemd
 291 Support: %SUPPORT_URL%
 292
 293 The virtual machine @NAME@ with its leader PID @LEADER@ has been
 294 shut down.
 295
 296 -- 36db2dfa5a9045e1bd4af5f93e1cf057
 297 Subject: DNSSEC mode has been turned off, as server doesn't support it
 298 Defined-By: systemd
 299 Support: %SUPPORT_URL%
 300 Documentation: man:systemd-resolved.service(8) resolved.conf(5)
 301
 302 The resolver service (systemd-resolved.service) has detected that the
 303 configured DNS server does not support DNSSEC, and DNSSEC validation has been
 304 turned off as result.
 305
 306 This event will take place if DNSSEC=allow-downgrade is configured in
 307 resolved.conf and the configured DNS server is incompatible with DNSSEC. Note
 308 that using this mode permits DNSSEC downgrade attacks, as an attacker might be
 309 able turn off DNSSEC validation on the system by inserting DNS replies in the
 310 communication channel that result in a downgrade like this.
 311
 312 This event might be indication that the DNS server is indeed incompatible with
 313 DNSSEC or that an attacker has successfully managed to stage such a downgrade
 314 attack.
 315
 316 -- 1675d7f172174098b1108bf8c7dc8f5d
 317 Subject: DNSSEC validation failed
 318 Defined-By: systemd
 319 Support: %SUPPORT_URL%
 320 Documentation: man:systemd-resolved.service(8)
 321
 322 A DNS query or resource record set failed DNSSEC validation. This is usually
 323 indication that the communication channel used was tampered with.
 324
 325 -- 4d4408cfd0d144859184d1e65d7c8a65
 326 Subject: A DNSSEC trust anchor has been revoked
 327 Defined-By: systemd
 328 Support: %SUPPORT_URL%
 329 Documentation: man:systemd-resolved.service(8)
 330
 331 A DNSSEC trust anchor has been revoked. A new trust anchor has to be
 332 configured, or the operating system needs to be updated, to provide an updated
 333 DNSSEC trust anchor.
 334
 335 -- 5eb03494b6584870a536b337290809b3
 336 Subject: Automatic restarting of a unit has been scheduled
 337 Defined-By: systemd
 338 Support: %SUPPORT_URL%
 339
 340 Automatic restarting of the unit @UNIT@ has been scheduled, as the result for
 341 the configured Restart= setting for the unit.
 342
 343 -- ae8f7b866b0347b9af31fe1c80b127c0
 344 Subject: Resources consumed by unit runtime
 345 Defined-By: systemd
 346 Support: %SUPPORT_URL%
 347
 348 The unit @UNIT@ completed and consumed the indicated resources.
 349
 350 -- 50876a9db00f4c40bde1a2ad381c3a1b
 351 Subject: The system is configured in a way that might cause problems
 352 Defined-By: systemd
 353 Support: %SUPPORT_URL%
 354
 355 The following "tags" are possible:
 356 - "split-usr" — /usr is a separate file system and was not mounted when systemd
 357   was booted
 358 - "cgroups-missing" — the kernel was compiled without cgroup support or access
 359   to expected interface files is resticted
 360 - "var-run-bad" — /var/run is not a symlink to /run
 361 - "overflowuid-not-65534" — the kernel user ID used for "unknown" users (with
 362   NFS or user namespaces) is not 65534
 363 - "overflowgid-not-65534" — the kernel group ID used for "unknown" users (with
 364   NFS or user namespaces) is not 65534
 365 Current system is tagged as @TAINT@.