catalog/systemd.catalog.in

   1 # SPDX-License-Identifier: LGPL-2.1-or-later
   2
   3 # Message catalog for systemd's own messages
   4
   5 # The catalog format is documented on
   6 # https://www.freedesktop.org/wiki/Software/systemd/catalog
   7
   8 # For an explanation why we do all this, see https://xkcd.com/1024/
   9
  10 -- f77379a8490b408bbe5f6940505a777b
  11 Subject: The journal has been started
  12 Defined-By: systemd
  13 Support: %SUPPORT_URL%
  14
  15 The system journal process has started up, opened the journal
  16 files for writing and is now ready to process requests.
  17
  18 -- d93fb3c9c24d451a97cea615ce59c00b
  19 Subject: The journal has been stopped
  20 Defined-By: systemd
  21 Support: %SUPPORT_URL%
  22
  23 The system journal process has shut down and closed all currently
  24 active journal files.
  25
  26 -- ec387f577b844b8fa948f33cad9a75e6
  27 Subject: Disk space used by the journal
  28 Defined-By: systemd
  29 Support: %SUPPORT_URL%
  30
  31 @JOURNAL_NAME@ (@JOURNAL_PATH@) is currently using @CURRENT_USE_PRETTY@.
  32 Maximum allowed usage is set to @MAX_USE_PRETTY@.
  33 Leaving at least @DISK_KEEP_FREE_PRETTY@ free (of currently available @DISK_AVAILABLE_PRETTY@ of disk space).
  34 Enforced usage limit is thus @LIMIT_PRETTY@, of which @AVAILABLE_PRETTY@ are still available.
  35
  36 The limits controlling how much disk space is used by the journal may
  37 be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
  38 RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
  39 /etc/systemd/journald.conf. See journald.conf(5) for details.
  40
  41 -- a596d6fe7bfa4994828e72309e95d61e
  42 Subject: Messages from a service have been suppressed
  43 Defined-By: systemd
  44 Support: %SUPPORT_URL%
  45 Documentation: man:journald.conf(5)
  46
  47 A service has logged too many messages within a time period. Messages
  48 from the service have been dropped.
  49
  50 Note that only messages from the service in question have been
  51 dropped, other services' messages are unaffected.
  52
  53 The limits controlling when messages are dropped may be configured
  54 with RateLimitIntervalSec= and RateLimitBurst= in
  55 /etc/systemd/journald.conf or LogRateLimitIntervalSec= and LogRateLimitBurst=
  56 in the unit file. See journald.conf(5) and systemd.exec(5) for details.
  57
  58 -- e9bf28e6e834481bb6f48f548ad13606
  59 Subject: Journal messages have been missed
  60 Defined-By: systemd
  61 Support: %SUPPORT_URL%
  62
  63 Kernel messages have been lost as the journal system has been unable
  64 to process them quickly enough.
  65
  66 -- fc2e22bc6ee647b6b90729ab34a250b1
  67 Subject: Process @COREDUMP_PID@ (@COREDUMP_COMM@) dumped core
  68 Defined-By: systemd
  69 Support: %SUPPORT_URL%
  70 Documentation: man:core(5)
  71
  72 Process @COREDUMP_PID@ (@COREDUMP_COMM@) crashed and dumped core.
  73
  74 This usually indicates a programming error in the crashing program and
  75 should be reported to its vendor as a bug.
  76
  77 -- 5aadd8e954dc4b1a8c954d63fd9e1137
  78 Subject: Core file was truncated to @SIZE_LIMIT@ bytes.
  79 Defined-By: systemd
  80 Support: %SUPPORT_URL%
  81 Documentation: man:coredump.conf(5)
  82
  83 The process had more memory mapped than the configured maximum for processing
  84 and storage by systemd-coredump(8). Only the first @SIZE_LIMIT@ bytes were
  85 saved. This core might still be usable, but various tools like gdb(1) will warn
  86 about the file being truncated.
  87
  88 -- 8d45620c1a4348dbb17410da57c60c66
  89 Subject: A new session @SESSION_ID@ has been created for user @USER_ID@
  90 Defined-By: systemd
  91 Support: %SUPPORT_URL%
  92 Documentation: sd-login(3)
  93
  94 A new session with the ID @SESSION_ID@ has been created for the user @USER_ID@.
  95
  96 The leading process of the session is @LEADER@.
  97
  98 -- 3354939424b4456d9802ca8333ed424a
  99 Subject: Session @SESSION_ID@ has been terminated
 100 Defined-By: systemd
 101 Support: %SUPPORT_URL%
 102 Documentation: sd-login(3)
 103
 104 A session with the ID @SESSION_ID@ has been terminated.
 105
 106 -- fcbefc5da23d428093f97c82a9290f7b
 107 Subject: A new seat @SEAT_ID@ is now available
 108 Defined-By: systemd
 109 Support: %SUPPORT_URL%
 110 Documentation: sd-login(3)
 111
 112 A new seat @SEAT_ID@ has been configured and is now available.
 113
 114 -- e7852bfe46784ed0accde04bc864c2d5
 115 Subject: Seat @SEAT_ID@ has now been removed
 116 Defined-By: systemd
 117 Support: %SUPPORT_URL%
 118 Documentation: sd-login(3)
 119
 120 A seat @SEAT_ID@ has been removed and is no longer available.
 121
 122 -- c7a787079b354eaaa9e77b371893cd27
 123 Subject: Time change
 124 Defined-By: systemd
 125 Support: %SUPPORT_URL%
 126
 127 The system clock has been changed to @REALTIME@ microseconds after January 1st, 1970.
 128
 129 -- 45f82f4aef7a4bbf942ce861d1f20990
 130 Subject: Time zone change to @TIMEZONE@
 131 Defined-By: systemd
 132 Support: %SUPPORT_URL%
 133
 134 The system timezone has been changed to @TIMEZONE@.
 135
 136 -- b07a249cd024414a82dd00cd181378ff
 137 Subject: System start-up is now complete
 138 Defined-By: systemd
 139 Support: %SUPPORT_URL%
 140
 141 All system services necessary queued for starting at boot have been
 142 started. Note that this does not mean that the machine is now idle as services
 143 might still be busy with completing start-up.
 144
 145 Kernel start-up required @KERNEL_USEC@ microseconds.
 146
 147 Initrd start-up required @INITRD_USEC@ microseconds.
 148
 149 Userspace start-up required @USERSPACE_USEC@ microseconds.
 150
 151 -- eed00a68ffd84e31882105fd973abdd1
 152 Subject: User manager start-up is now complete
 153 Defined-By: systemd
 154 Support: %SUPPORT_URL%
 155
 156 The user manager instance for user @_UID@ has been started. All services queued
 157 for starting have been started. Note that other services might still be starting
 158 up or be started at any later time.
 159
 160 Startup of the manager took @USERSPACE_USEC@ microseconds.
 161
 162 -- 6bbd95ee977941e497c48be27c254128
 163 Subject: System sleep state @SLEEP@ entered
 164 Defined-By: systemd
 165 Support: %SUPPORT_URL%
 166
 167 The system has now entered the @SLEEP@ sleep state.
 168
 169 -- 8811e6df2a8e40f58a94cea26f8ebf14
 170 Subject: System sleep state @SLEEP@ left
 171 Defined-By: systemd
 172 Support: %SUPPORT_URL%
 173
 174 The system has now left the @SLEEP@ sleep state.
 175
 176 -- 98268866d1d54a499c4e98921d93bc40
 177 Subject: System shutdown initiated
 178 Defined-By: systemd
 179 Support: %SUPPORT_URL%
 180
 181 System shutdown has been initiated. The shutdown has now begun and
 182 all system services are terminated and all file systems unmounted.
 183
 184 -- c14aaf76ec284a5fa1f105f88dfb061c
 185 Subject: System factory reset initiated
 186 Defined-By: systemd
 187 Support: %SUPPORT_URL%
 188
 189 System factory reset has been initiated. The precise operation this
 190 executes is implementation-defined, but typically has the effect of
 191 reverting the system's state and configuration to vendor defaults.
 192
 193 -- d9ec5e95e4b646aaaea2fd05214edbda
 194 Subject: Container init crashed
 195 Defined-By: systemd
 196 Support: %SUPPORT_URL%
 197
 198 Container init has crashed and exited.
 199 The details of the crash can be obtained from the container manager.
 200
 201 -- 3ed0163e868a4417ab8b9e210407a96c
 202 Subject: System reboot failed after crash
 203 Defined-By: systemd
 204 Support: %SUPPORT_URL%
 205
 206 Reboot has failed when systemd attempted to reboot after a crash.
 207
 208 -- 645c735537634ae0a32b15a7c6cba7d4
 209 Subject: Init execution froze
 210 Defined-By: systemd
 211 Support: %SUPPORT_URL%
 212
 213 Systemd froze execution after fatal error.
 214
 215 -- 5addb3a06a734d3396b794bf98fb2d01
 216 Subject: Init received fatal signal while coredump is disabled
 217 Defined-By: systemd
 218 Support: %SUPPORT_URL%
 219
 220 Systemd received fatal signal, but core dumping is disabled.
 221
 222 -- 5c9e98de4ab94c6a9d04d0ad793bd903
 223 Subject: Init received fatal signal but fork failed
 224 Defined-By: systemd
 225 Support: %SUPPORT_URL%
 226
 227 Systemd received fatal signal, but failed to fork to dump the core.
 228
 229 -- 5e6f1f5e4db64a0eaee3368249d20b94
 230 Subject: Init received fatal signal from unknown sender process
 231 Defined-By: systemd
 232 Support: %SUPPORT_URL%
 233
 234 -- 83f84b35ee264f74a3896a9717af34cb
 235 Subject: Init received fatal signal from our own process
 236 Defined-By: systemd
 237 Support: %SUPPORT_URL%
 238
 239 -- 3a73a98baf5b4b199929e3226c0be783
 240 Subject: Init received fatal signal from other process
 241 Defined-By: systemd
 242 Support: %SUPPORT_URL%
 243
 244 -- 2ed18d4f78ca47f0a9bc25271c26adb4
 245 Subject: Init received fatal signal but waitpid() failed
 246 Defined-By: systemd
 247 Support: %SUPPORT_URL%
 248
 249 Systemd received fatal signal, but waitpid() failed when
 250 trying to dump the core.
 251
 252 -- 56b1cd96f24246c5b607666fda952356
 253 Subject: Init received fatal signal but coredump failed
 254 Defined-By: systemd
 255 Support: %SUPPORT_URL%
 256
 257 -- 4ac7566d4d7548f4981f629a28f0f829
 258 Subject: Init received fatal signal and dumped core
 259 Defined-By: systemd
 260 Support: %SUPPORT_URL%
 261
 262 -- 38e8b1e039ad469291b18b44c553a5b7
 263 Subject: Init failed to fork crash shell
 264 Defined-By: systemd
 265 Support: %SUPPORT_URL%
 266
 267 Systemd crashed and failed to fork off crash shell.
 268
 269 -- 872729b47dbe473eb768ccecd477beda
 270 Subject: Crash shell failed to execute
 271 Defined-By: systemd
 272 Support: %SUPPORT_URL%
 273
 274 Systemd crashed and failed to spawn crash shell.
 275
 276 -- 658a67adc1c940b3b3316e7e8628834a
 277 Subject: Manager failed to load SELinux policy
 278 Defined-By: systemd
 279 Support: %SUPPORT_URL%
 280
 281 -- e6f456bd92004d9580160b2207555186
 282 Subject: Battery level critically low, waiting for charger
 283 Defined-By: systemd
 284 Support: %SUPPORT_URL%
 285
 286 Battery level is critically low. Please connect your charger
 287 or the system will power off in 10 seconds.
 288
 289 -- 267437d33fdd41099ad76221cc24a335
 290 Subject: Battery level critically low, powering off
 291 Defined-By: systemd
 292 Support: %SUPPORT_URL%
 293
 294 -- 79e05b67bc4545d1922fe47107ee60c5
 295 Subject: Manager failed to run main loop
 296 Defined-By: systemd
 297 Support: %SUPPORT_URL%
 298
 299 -- dbb136b10ef4457ba47a795d62f108c9
 300 Subject: User manager failed to determine $XDG_RUNTIME_DIR path
 301 Defined-By: systemd
 302 Support: %SUPPORT_URL%
 303
 304 -- ed158c2df8884fa584eead2d902c1032
 305 Subject: Init failed to drop capability bounding set of usermode helpers
 306 Defined-By: systemd
 307 Support: %SUPPORT_URL%
 308
 309 -- 42695b500df048298bee37159caa9f2e
 310 Subject: Init failed to drop capability bounding set
 311 Defined-By: systemd
 312 Support: %SUPPORT_URL%
 313
 314 -- bfc2430724ab44499735b4f94cca9295
 315 Subject: User manager failed to disable new privileges
 316 Defined-By: systemd
 317 Support: %SUPPORT_URL%
 318
 319 -- 59288af523be43a28d494e41e26e4510
 320 Subject: Manager failed to start default target
 321 Defined-By: systemd
 322 Support: %SUPPORT_URL%
 323
 324 -- 689b4fcc97b4486ea5da92db69c9e314
 325 Subject: Manager failed to isolate default target
 326 Defined-By: systemd
 327 Support: %SUPPORT_URL%
 328
 329 -- 5ed836f1766f4a8a9fc5da45aae23b29
 330 Subject: Manager failed to collect passed file descriptors
 331 Defined-By: systemd
 332 Support: %SUPPORT_URL%
 333
 334 -- 6a40fbfbd2ba4b8db02fb40c9cd090d7
 335 Subject: Init failed to fix up environment variables
 336 Defined-By: systemd
 337 Support: %SUPPORT_URL%
 338
 339 -- 0e54470984ac419689743d957a119e2e
 340 Subject: Failed to allocate manager object
 341 Defined-By: systemd
 342 Support: %SUPPORT_URL%
 343
 344 -- d67fa9f847aa4b048a2ae33535331adb
 345 Subject: Manager failed to write Smack onlycap list
 346 Defined-By: systemd
 347 Support: %SUPPORT_URL%
 348
 349 -- af55a6f75b544431b72649f36ff6d62c
 350 Subject: Critical error while doing system shutdown
 351 Defined-By: systemd
 352 Support: %SUPPORT_URL%
 353
 354 -- d18e0339efb24a068d9c1060221048c2
 355 Subject: Init failed to fork off valgrind helper
 356 Defined-By: systemd
 357 Support: %SUPPORT_URL%
 358
 359 -- 7d4958e842da4a758f6c1cdc7b36dcc5
 360 Subject: A start job for unit @UNIT@ has begun execution
 361 Defined-By: systemd
 362 Support: %SUPPORT_URL%
 363
 364 A start job for unit @UNIT@ has begun execution.
 365
 366 The job identifier is @JOB_ID@.
 367
 368 -- 39f53479d3a045ac8e11786248231fbf
 369 Subject: A start job for unit @UNIT@ has finished successfully
 370 Defined-By: systemd
 371 Support: %SUPPORT_URL%
 372
 373 A start job for unit @UNIT@ has finished successfully.
 374
 375 The job identifier is @JOB_ID@.
 376
 377 -- be02cf6855d2428ba40df7e9d022f03d
 378 Subject: A start job for unit @UNIT@ has failed
 379 Defined-By: systemd
 380 Support: %SUPPORT_URL%
 381
 382 A start job for unit @UNIT@ has finished with a failure.
 383
 384 The job identifier is @JOB_ID@ and the job result is @JOB_RESULT@.
 385
 386 -- de5b426a63be47a7b6ac3eaac82e2f6f
 387 Subject: A stop job for unit @UNIT@ has begun execution
 388 Defined-By: systemd
 389 Support: %SUPPORT_URL%
 390
 391 A stop job for unit @UNIT@ has begun execution.
 392
 393 The job identifier is @JOB_ID@.
 394
 395 -- 9d1aaa27d60140bd96365438aad20286
 396 Subject: A stop job for unit @UNIT@ has finished
 397 Defined-By: systemd
 398 Support: %SUPPORT_URL%
 399
 400 A stop job for unit @UNIT@ has finished.
 401
 402 The job identifier is @JOB_ID@ and the job result is @JOB_RESULT@.
 403
 404 -- d34d037fff1847e6ae669a370e694725
 405 Subject: A reload job for unit @UNIT@ has begun execution
 406 Defined-By: systemd
 407 Support: %SUPPORT_URL%
 408
 409 A reload job for unit @UNIT@ has begun execution.
 410
 411 The job identifier is @JOB_ID@.
 412
 413 -- 7b05ebc668384222baa8881179cfda54
 414 Subject: A reload job for unit @UNIT@ has finished
 415 Defined-By: systemd
 416 Support: %SUPPORT_URL%
 417
 418 A reload job for unit @UNIT@ has finished.
 419
 420 The job identifier is @JOB_ID@ and the job result is @JOB_RESULT@.
 421
 422 -- 641257651c1b4ec9a8624d7a40a9e1e7
 423 Subject: Process @EXECUTABLE@ could not be executed
 424 Defined-By: systemd
 425 Support: %SUPPORT_URL%
 426
 427 The process @EXECUTABLE@ could not be executed and failed.
 428
 429 The error number returned by this process is @ERRNO@.
 430
 431 -- 0027229ca0644181a76c4e92458afa2e
 432 Subject: One or more messages could not be forwarded to syslog
 433 Defined-By: systemd
 434 Support: %SUPPORT_URL%
 435
 436 One or more messages could not be forwarded to the syslog service
 437 running side-by-side with journald. This usually indicates that the
 438 syslog implementation has not been able to keep up with the speed of
 439 messages queued.
 440
 441 -- 1dee0369c7fc4736b7099b38ecb46ee7
 442 Subject: Mount point is not empty
 443 Defined-By: systemd
 444 Support: %SUPPORT_URL%
 445
 446 The directory @WHERE@ is specified as the mount point (second field in
 447 /etc/fstab or Where= field in systemd unit file) and is not empty.
 448 This does not interfere with mounting, but the pre-exisiting files in
 449 this directory become inaccessible. To see those over-mounted files,
 450 please manually mount the underlying file system to a secondary
 451 location.
 452
 453 -- 24d8d4452573402496068381a6312df2
 454 Subject: A virtual machine or container has been started
 455 Defined-By: systemd
 456 Support: %SUPPORT_URL%
 457
 458 The virtual machine @NAME@ with its leader PID @LEADER@ has been
 459 started is now ready to use.
 460
 461 -- 58432bd3bace477cb514b56381b8a758
 462 Subject: A virtual machine or container has been terminated
 463 Defined-By: systemd
 464 Support: %SUPPORT_URL%
 465
 466 The virtual machine @NAME@ with its leader PID @LEADER@ has been
 467 shut down.
 468
 469 -- 36db2dfa5a9045e1bd4af5f93e1cf057
 470 Subject: DNSSEC mode has been turned off, as server doesn't support it
 471 Defined-By: systemd
 472 Support: %SUPPORT_URL%
 473 Documentation: man:systemd-resolved.service(8)
 474 Documentation: man:resolved.conf(5)
 475
 476 The resolver service (systemd-resolved.service) has detected that the
 477 configured DNS server does not support DNSSEC, and DNSSEC validation has been
 478 turned off as result.
 479
 480 This event will take place if DNSSEC=allow-downgrade is configured in
 481 resolved.conf and the configured DNS server is incompatible with DNSSEC. Note
 482 that using this mode permits DNSSEC downgrade attacks, as an attacker might be
 483 able turn off DNSSEC validation on the system by inserting DNS replies in the
 484 communication channel that result in a downgrade like this.
 485
 486 This event might be indication that the DNS server is indeed incompatible with
 487 DNSSEC or that an attacker has successfully managed to stage such a downgrade
 488 attack.
 489
 490 -- 1675d7f172174098b1108bf8c7dc8f5d
 491 Subject: DNSSEC validation failed
 492 Defined-By: systemd
 493 Support: %SUPPORT_URL%
 494 Documentation: man:systemd-resolved.service(8)
 495
 496 A DNS query or resource record set failed DNSSEC validation. This is usually
 497 indication that the communication channel used was tampered with.
 498
 499 -- 4d4408cfd0d144859184d1e65d7c8a65
 500 Subject: A DNSSEC trust anchor has been revoked
 501 Defined-By: systemd
 502 Support: %SUPPORT_URL%
 503 Documentation: man:systemd-resolved.service(8)
 504
 505 A DNSSEC trust anchor has been revoked. A new trust anchor has to be
 506 configured, or the operating system needs to be updated, to provide an updated
 507 DNSSEC trust anchor.
 508
 509 -- 5eb03494b6584870a536b337290809b3
 510 Subject: Automatic restarting of a unit has been scheduled
 511 Defined-By: systemd
 512 Support: %SUPPORT_URL%
 513
 514 Automatic restarting of the unit @UNIT@ has been scheduled, as the result for
 515 the configured Restart= setting for the unit.
 516
 517 -- ae8f7b866b0347b9af31fe1c80b127c0
 518 Subject: Resources consumed by unit runtime
 519 Defined-By: systemd
 520 Support: %SUPPORT_URL%
 521
 522 The unit @UNIT@ completed and consumed the indicated resources.
 523
 524 -- 7ad2d189f7e94e70a38c781354912448
 525 Subject: Unit succeeded
 526 Defined-By: systemd
 527 Support: %SUPPORT_URL%
 528
 529 The unit @UNIT@ has successfully entered the 'dead' state.
 530
 531 -- 0e4284a0caca4bfc81c0bb6786972673
 532 Subject: Unit skipped
 533 Defined-By: systemd
 534 Support: %SUPPORT_URL%
 535
 536 The unit @UNIT@ was skipped due to an ExecCondition= command failure, and has
 537 entered the 'dead' state with result '@UNIT_RESULT@'.
 538
 539 -- d9b373ed55a64feb8242e02dbe79a49c
 540 Subject: Unit failed
 541 Defined-By: systemd
 542 Support: %SUPPORT_URL%
 543
 544 The unit @UNIT@ has entered the 'failed' state with result '@UNIT_RESULT@'.
 545
 546 -- 98e322203f7a4ed290d09fe03c09fe15
 547 Subject: Unit process exited
 548 Defined-By: systemd
 549 Support: %SUPPORT_URL%
 550
 551 An @COMMAND@= process belonging to unit @UNIT@ has exited.
 552
 553 The process' exit code is '@EXIT_CODE@' and its exit status is @EXIT_STATUS@.
 554
 555 -- 50876a9db00f4c40bde1a2ad381c3a1b
 556 Subject: The system is configured in a way that might cause problems
 557 Defined-By: systemd
 558 Support: %SUPPORT_URL%
 559
 560 The following "tags" are possible:
 561 - "unmerged-usr" - /bin, /sbin, /lib* are not symlinks to their counterparts
 562   under /usr/
 563 - "unmerged-bin" - /usr/sbin is not a symlink to /usr/bin/
 564 - "var-run-bad" — /var/run is not a symlink to /run/
 565 - "cgroupsv1" - the system is using the deprecated cgroup v1 hierarchy
 566 - "local-hwclock" - the local hardware clock (RTC) is configured to be in
 567   local time rather than UTC
 568 - "support-ended" - the system is running past the end of support declared
 569   by the vendor
 570 - "old-kernel" - the system is running a kernel version that is older than
 571   the minimum supported by this version of systemd
 572 - "overflowuid-not-65534" — the kernel user ID used for "unknown" users (with
 573   NFS or user namespaces) is not 65534
 574 - "overflowgid-not-65534" — the kernel group ID used for "unknown" users (with
 575   NFS or user namespaces) is not 65534
 576 - "short-uid-range" - the UID range assigned to the running systemd instance
 577   covers less than 0…65534
 578 - "short-gid-range" - the GID range assigned to the running systemd instance
 579   covers less than 0…65534
 580 Current system is tagged as @TAINT@.
 581
 582 -- fe6faa94e7774663a0da52717891d8ef
 583 Subject: A process of @UNIT@ unit has been killed by the OOM killer.
 584 Defined-By: systemd
 585 Support: %SUPPORT_URL%
 586
 587 A process of unit @UNIT has been killed by the Linux kernel out-of-memory (OOM)
 588 killer logic. This usually indicates that the system is low on memory and that
 589 memory needed to be freed. A process associated with @UNIT@ has been determined
 590 as the best process to terminate and has been forcibly terminated by the
 591 kernel.
 592
 593 Note that the memory pressure might or might not have been caused by @UNIT@.
 594
 595 -- b61fdac612e94b9182285b998843061f
 596 Subject: Accepting user/group name @USER_GROUP_NAME@, which does not match strict user/group name rules.
 597 Defined-By: systemd
 598 Support: %SUPPORT_URL%
 599 Documentation: https://systemd.io/USER_NAMES
 600
 601 The user/group name @USER_GROUP_NAME@ has been specified, which is accepted
 602 according the relaxed user/group name rules, but does not qualify under the
 603 strict rules.
 604
 605 The strict user/group name rules written as regular expression are:
 606
 607 ^[a-zA-Z_][a-zA-Z0-9_-]{0,30}$
 608
 609 The relaxed user/group name rules accept all names, except for the empty
 610 string; names containing NUL bytes, control characters, colon or slash
 611 characters; names not valid UTF-8; names with leading or trailing whitespace;
 612 the strings "." or ".."; fully numeric strings, or strings beginning in a
 613 hyphen and otherwise fully numeric.
 614
 615 -- 1b3bb94037f04bbf81028e135a12d293
 616 Subject: Failed to generate valid unit name from path '@MOUNT_POINT@'.
 617 Defined-By: systemd
 618 Support: %SUPPORT_URL%
 619
 620 The following mount point path could not be converted into a valid .mount
 621 unit name:
 622
 623     @MOUNT_POINT@
 624
 625 Typically this means that the path to the mount point is longer than allowed
 626 for valid unit names.
 627
 628 systemd dynamically synthesizes .mount units for all mount points appearing on
 629 the system. For that a simple escaping algorithm is applied: the absolute path
 630 name is used, with all "/" characters replaced by "-" (the leading one is
 631 removed). Moreover, any non-alphanumeric characters (as well as any of ":",
 632 "-", "_", ".", "\") are replaced by "\xNN" where "NN" is the hexadecimal code
 633 of the character. Finally, ".mount" is suffixed. The resulting string must be
 634 under 256 characters in length to be a valid unit name. This restriction is
 635 made in order for all unit names to also be suitable as file names. If a mount
 636 point appears that — after escaping — is longer than this limit it cannot be
 637 mapped to a unit. In this case systemd will refrain from synthesizing a unit
 638 and cannot be used to manage the mount point. It will not appear in the service
 639 manager's unit table and thus also not be torn down safely and automatically at
 640 system shutdown.
 641
 642 It is generally recommended to avoid such overly long mount point paths, or —
 643 if used anyway – manage them independently of systemd, i.e. establish them as
 644 well as tear them down automatically at system shutdown by other software.
 645
 646 -- b480325f9c394a7b802c231e51a2752c
 647 Subject: Special user @OFFENDING_USER@ configured, this is not safe!
 648 Defined-By: systemd
 649 Support: %SUPPORT_URL%
 650 Documentation: https://systemd.io/UIDS-GIDS
 651
 652 The unit @UNIT@ is configured to use User=@OFFENDING_USER@.
 653
 654 This is not safe. The @OFFENDING_USER@ user's main purpose on Linux-based
 655 operating systems is to be the owner of files that otherwise cannot be mapped
 656 to any local user. It's used by the NFS client and Linux user namespacing,
 657 among others. By running a unit's processes under the identity of this user
 658 they might possibly get read and even write access to such files that cannot
 659 otherwise be mapped.
 660
 661 It is strongly recommended to avoid running services under this user identity,
 662 in particular on systems using NFS or running containers. Allocate a user ID
 663 specific to this service, either statically via systemd-sysusers or dynamically
 664 via the DynamicUser= service setting.
 665
 666 -- 1c0454c1bd2241e0ac6fefb4bc631433
 667 Subject: systemd-udev-settle.service is deprecated.
 668 Defined-By: systemd
 669 Support: %SUPPORT_URL%
 670
 671 Usage of the systemd service unit systemd-udev-settle.service is deprecated. It
 672 inserts artificial delays into the boot process without providing the
 673 guarantees other subsystems traditionally assumed it provides. Relying on this
 674 service is racy, and it is generally a bug to make use of it and depend on it.
 675
 676 Traditionally, this service's job was to wait until all devices a system
 677 possesses have been fully probed and initialized, delaying boot until this
 678 phase is completed. However, today's systems and hardware generally don't work
 679 this way anymore, hardware today may show up any time and take any time to be
 680 probed and initialized. Thus, in the general case, it's no longer possible to
 681 correctly delay boot until "all devices" have been processed, as it is not
 682 clear what "all devices" means and when they have been found. This is in
 683 particular the case if USB hardware or network-attached hardware is used.
 684
 685 Modern software that requires some specific hardware (such as a network device
 686 or block device) to operate should only wait for the specific devices it needs
 687 to show up, and otherwise operate asynchronously initializing devices as they
 688 appear during boot and during runtime without delaying the boot process.
 689
 690 It is a defect of the software in question if it doesn't work this way, and
 691 still pulls systemd-udev-settle.service into the boot process.
 692
 693 Please file a bug report against the following units, with a request for it to
 694 be updated to operate in a hotplug fashion without depending on
 695 systemd-udev-settle.service:
 696
 697     @OFFENDING_UNITS@
 698
 699 -- 7c8a41f37b764941a0e1780b1be2f037
 700 Subject: Initial clock synchronization
 701 Defined-By: systemd
 702 Support: %SUPPORT_URL%
 703
 704 For the first time during the current boot an NTP synchronization has been
 705 acquired and the local system clock adjustment has been initiated.
 706
 707 -- 7db73c8af0d94eeb822ae04323fe6ab6
 708 Subject: Initial clock bump
 709 Defined-By: systemd
 710 Support: %SUPPORT_URL%
 711
 712 The system clock has been advanced based on a timestamp file on disk, in order
 713 to ensure it remains roughly monotonic – even across reboots – if an RTC is not
 714 available or is unreliable.
 715
 716 -- 3f7d5ef3e54f4302b4f0b143bb270cab
 717 Subject: TPM PCR Extended
 718 Defined-By: systemd
 719 Support: %SUPPORT_URL%
 720
 721 The Trusted Platform Module's (TPM) Platform Configuration Register (PCR)
 722 @PCR@, on banks @BANKS@, has been extended with the string '@MEASURING@'.
 723
 724 Whenever the system transitions to a new runtime phase, the specified PCR is
 725 extended with a different string, to ensure that security policies for
 726 TPM-bound secrets and other resources are limited to specific phases of the
 727 runtime.
 728
 729 -- f9b0be465ad540d0850ad32172d57c21
 730 Subject: Memory Trimmed
 731 Defined-By: systemd
 732 Support: %SUPPORT_URL%
 733
 734 Memory of process @_PID@ (@_COMM@) has been trimmed.
 735
 736 Either on user request or as result of a memory pressure event, memory of the
 737 process has been trimmed, returning unneeded allocation caches and other
 738 resources back to the OS kernel, making them available for other components of
 739 the OS.
 740
 741 @TRIMMED_BYTES@ of memory were returned to the OS, which took @TRIMMED_USEC@
 742 micro-seconds (μs).
 743
 744 -- a8fa8dacdb1d443e9503b8be367a6adb
 745 Subject: SysV Service Found
 746 Defined-By: systemd
 747 Support: %SUPPORT_URL%
 748
 749 A System V service script @SYSVSCRIPT@ has been found on the system that lacks
 750 a native systemd unit. An automatic unit file @UNIT@ has been generated for
 751 compatibility.
 752
 753 Note that these automatically generated compatibility unit files cannot replace
 754 native unit files as they generally slow down the system (by creating
 755 unnecessary, additional synchronization points), are less robust (as SysV services
 756 cannot properly be lifecycle tracked or automatically restarted) and less
 757 secure (as no sandboxing restrictions can be enforced).
 758
 759 Compatibility support for System V services in systemd is deprecated. Please
 760 make sure to update the package in question to provide proper, native systemd
 761 unit files. Contact vendor if necessary. Compatibility support for System V
 762 services is deprecated and will be removed soon.
 763
 764 -- 187c62eb1e7f463bb530394f52cb090f
 765 Subject: A Portable Service has been attached
 766 Defined-By: systemd
 767 Support: %SUPPORT_URL%
 768 Documentation: https://systemd.io/PORTABLE_SERVICES/
 769
 770 A new Portable Service @PORTABLE_ROOT@ (with extensions: @PORTABLE_EXTENSION@) has
 771 been attached to the system and is now available for use. The list of attached
 772 Portable Services can be queried with 'portablectl list'.
 773
 774 -- 76c5c754d628490d8ecba4c9d042112b
 775 Subject: A Portable Service has been detached
 776 Defined-By: systemd
 777 Support: %SUPPORT_URL%
 778 Documentation: https://systemd.io/PORTABLE_SERVICES/
 779
 780 A Portable Service @PORTABLE_ROOT@ (with extensions: @PORTABLE_EXTENSION@) has been
 781 detached from the system and is no longer available for use. The list of attached
 782 Portable Services can be queried with 'portablectl list'.