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