mirror of
https://github.com/systemd/systemd-stable.git
synced 2024-12-23 17:34:00 +03:00
4b930ded83
Let's allow distros to change the support URL to expose in catalog entries by default. It doesn't make sense to direct end-users to the upstream project for common errors. This adds a --with-support-url= switch to configure, which allows overriding the default at build-time. Fixes: #2516
335 lines
11 KiB
Plaintext
335 lines
11 KiB
Plaintext
# This file is part of systemd.
|
|
#
|
|
# Copyright 2012 Lennart Poettering
|
|
#
|
|
# systemd is free software; you can redistribute it and/or modify it
|
|
# under the terms of the GNU Lesser General Public License as published by
|
|
# the Free Software Foundation; either version 2.1 of the License, or
|
|
# (at your option) any later version.
|
|
#
|
|
# systemd is distributed in the hope that it will be useful, but
|
|
# WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
# Lesser General Public License for more details.
|
|
#
|
|
# You should have received a copy of the GNU Lesser General Public License
|
|
# along with systemd; If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
# Message catalog for systemd's own messages
|
|
|
|
# The catalog format is documented on
|
|
# http://www.freedesktop.org/wiki/Software/systemd/catalog
|
|
|
|
# For an explanation why we do all this, see https://xkcd.com/1024/
|
|
|
|
-- f77379a8490b408bbe5f6940505a777b
|
|
Subject: The journal has been started
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
The system journal process has started up, opened the journal
|
|
files for writing and is now ready to process requests.
|
|
|
|
-- d93fb3c9c24d451a97cea615ce59c00b
|
|
Subject: The journal has been stopped
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
The system journal process has shut down and closed all currently
|
|
active journal files.
|
|
|
|
-- ec387f577b844b8fa948f33cad9a75e6
|
|
Subject: Disk space used by the journal
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
@JOURNAL_NAME@ (@JOURNAL_PATH@) is currently using @CURRENT_USE_PRETTY@.
|
|
Maximum allowed usage is set to @MAX_USE_PRETTY@.
|
|
Leaving at least @DISK_KEEP_FREE_PRETTY@ free (of currently available @DISK_AVAILABLE_PRETTY@ of disk space).
|
|
Enforced usage limit is thus @LIMIT_PRETTY@, of which @AVAILABLE_PRETTY@ are still available.
|
|
|
|
The limits controlling how much disk space is used by the journal may
|
|
be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
|
|
RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
|
|
/etc/systemd/journald.conf. See journald.conf(5) for details.
|
|
|
|
-- a596d6fe7bfa4994828e72309e95d61e
|
|
Subject: Messages from a service have been suppressed
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
Documentation: man:journald.conf(5)
|
|
|
|
A service has logged too many messages within a time period. Messages
|
|
from the service have been dropped.
|
|
|
|
Note that only messages from the service in question have been
|
|
dropped, other services' messages are unaffected.
|
|
|
|
The limits controlling when messages are dropped may be configured
|
|
with RateLimitIntervalSec= and RateLimitBurst= in
|
|
/etc/systemd/journald.conf. See journald.conf(5) for details.
|
|
|
|
-- e9bf28e6e834481bb6f48f548ad13606
|
|
Subject: Journal messages have been missed
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
Kernel messages have been lost as the journal system has been unable
|
|
to process them quickly enough.
|
|
|
|
-- fc2e22bc6ee647b6b90729ab34a250b1
|
|
Subject: Process @COREDUMP_PID@ (@COREDUMP_COMM@) dumped core
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
Documentation: man:core(5)
|
|
|
|
Process @COREDUMP_PID@ (@COREDUMP_COMM@) crashed and dumped core.
|
|
|
|
This usually indicates a programming error in the crashing program and
|
|
should be reported to its vendor as a bug.
|
|
|
|
-- fc2e22bc6ee647b6b90729ab34a250b1 de
|
|
Subject: Speicherabbild für Prozess @COREDUMP_PID@ (@COREDUMP_COMM) generiert
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
Documentation: man:core(5)
|
|
|
|
Prozess @COREDUMP_PID@ (@COREDUMP_COMM@) ist abgebrochen worden und
|
|
ein Speicherabbild wurde generiert.
|
|
|
|
Üblicherweise ist dies ein Hinweis auf einen Programmfehler und sollte
|
|
als Fehler dem jeweiligen Hersteller gemeldet werden.
|
|
|
|
-- 8d45620c1a4348dbb17410da57c60c66
|
|
Subject: A new session @SESSION_ID@ has been created for user @USER_ID@
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
|
|
|
|
A new session with the ID @SESSION_ID@ has been created for the user @USER_ID@.
|
|
|
|
The leading process of the session is @LEADER@.
|
|
|
|
-- 3354939424b4456d9802ca8333ed424a
|
|
Subject: Session @SESSION_ID@ has been terminated
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
|
|
|
|
A session with the ID @SESSION_ID@ has been terminated.
|
|
|
|
-- fcbefc5da23d428093f97c82a9290f7b
|
|
Subject: A new seat @SEAT_ID@ is now available
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
|
|
|
|
A new seat @SEAT_ID@ has been configured and is now available.
|
|
|
|
-- e7852bfe46784ed0accde04bc864c2d5
|
|
Subject: Seat @SEAT_ID@ has now been removed
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
|
|
|
|
A seat @SEAT_ID@ has been removed and is no longer available.
|
|
|
|
-- c7a787079b354eaaa9e77b371893cd27
|
|
Subject: Time change
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
The system clock has been changed to @REALTIME@ microseconds after January 1st, 1970.
|
|
|
|
-- c7a787079b354eaaa9e77b371893cd27 de
|
|
Subject: Zeitänderung
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
Die System-Zeit wurde geändert auf @REALTIME@ Mikrosekunden nach dem 1. Januar 1970.
|
|
|
|
-- 45f82f4aef7a4bbf942ce861d1f20990
|
|
Subject: Time zone change to @TIMEZONE@
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
The system timezone has been changed to @TIMEZONE@.
|
|
|
|
-- b07a249cd024414a82dd00cd181378ff
|
|
Subject: System start-up is now complete
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
All system services necessary queued for starting at boot have been
|
|
successfully started. Note that this does not mean that the machine is
|
|
now idle as services might still be busy with completing start-up.
|
|
|
|
Kernel start-up required @KERNEL_USEC@ microseconds.
|
|
|
|
Initial RAM disk start-up required @INITRD_USEC@ microseconds.
|
|
|
|
Userspace start-up required @USERSPACE_USEC@ microseconds.
|
|
|
|
-- 6bbd95ee977941e497c48be27c254128
|
|
Subject: System sleep state @SLEEP@ entered
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
The system has now entered the @SLEEP@ sleep state.
|
|
|
|
-- 8811e6df2a8e40f58a94cea26f8ebf14
|
|
Subject: System sleep state @SLEEP@ left
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
The system has now left the @SLEEP@ sleep state.
|
|
|
|
-- 98268866d1d54a499c4e98921d93bc40
|
|
Subject: System shutdown initiated
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
Systemd shutdown has been initiated. The shutdown has now begun and
|
|
all system services are terminated and all file systems unmounted.
|
|
|
|
-- 7d4958e842da4a758f6c1cdc7b36dcc5
|
|
Subject: Unit @UNIT@ has begun start-up
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
Unit @UNIT@ has begun starting up.
|
|
|
|
-- 39f53479d3a045ac8e11786248231fbf
|
|
Subject: Unit @UNIT@ has finished start-up
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
Unit @UNIT@ has finished starting up.
|
|
|
|
The start-up result is @RESULT@.
|
|
|
|
-- de5b426a63be47a7b6ac3eaac82e2f6f
|
|
Subject: Unit @UNIT@ has begun shutting down
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
Unit @UNIT@ has begun shutting down.
|
|
|
|
-- 9d1aaa27d60140bd96365438aad20286
|
|
Subject: Unit @UNIT@ has finished shutting down
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
Unit @UNIT@ has finished shutting down.
|
|
|
|
-- be02cf6855d2428ba40df7e9d022f03d
|
|
Subject: Unit @UNIT@ has failed
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
Unit @UNIT@ has failed.
|
|
|
|
The result is @RESULT@.
|
|
|
|
-- d34d037fff1847e6ae669a370e694725
|
|
Subject: Unit @UNIT@ has begun reloading its configuration
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
Unit @UNIT@ has begun reloading its configuration
|
|
|
|
-- 7b05ebc668384222baa8881179cfda54
|
|
Subject: Unit @UNIT@ has finished reloading its configuration
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
Unit @UNIT@ has finished reloading its configuration
|
|
|
|
The result is @RESULT@.
|
|
|
|
-- 641257651c1b4ec9a8624d7a40a9e1e7
|
|
Subject: Process @EXECUTABLE@ could not be executed
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
The process @EXECUTABLE@ could not be executed and failed.
|
|
|
|
The error number returned by this process is @ERRNO@.
|
|
|
|
-- 0027229ca0644181a76c4e92458afa2e
|
|
Subject: One or more messages could not be forwarded to syslog
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
One or more messages could not be forwarded to the syslog service
|
|
running side-by-side with journald. This usually indicates that the
|
|
syslog implementation has not been able to keep up with the speed of
|
|
messages queued.
|
|
|
|
-- 1dee0369c7fc4736b7099b38ecb46ee7
|
|
Subject: Mount point is not empty
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
The directory @WHERE@ is specified as the mount point (second field in
|
|
/etc/fstab or Where= field in systemd unit file) and is not empty.
|
|
This does not interfere with mounting, but the pre-exisiting files in
|
|
this directory become inaccessible. To see those over-mounted files,
|
|
please manually mount the underlying file system to a secondary
|
|
location.
|
|
|
|
-- 24d8d4452573402496068381a6312df2
|
|
Subject: A virtual machine or container has been started
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
The virtual machine @NAME@ with its leader PID @LEADER@ has been
|
|
started is now ready to use.
|
|
|
|
-- 58432bd3bace477cb514b56381b8a758
|
|
Subject: A virtual machine or container has been terminated
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
|
|
The virtual machine @NAME@ with its leader PID @LEADER@ has been
|
|
shut down.
|
|
|
|
-- 36db2dfa5a9045e1bd4af5f93e1cf057
|
|
Subject: DNSSEC mode has been turned off, as server doesn't support it
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
Documentation: man:systemd-resolved.service(8) resolved.conf(5)
|
|
|
|
The resolver service (systemd-resolved.service) has detected that the
|
|
configured DNS server does not support DNSSEC, and DNSSEC validation has been
|
|
turned off as result.
|
|
|
|
This event will take place if DNSSEC=allow-downgrade is configured in
|
|
resolved.conf and the configured DNS server is incompatible with DNSSEC. Note
|
|
that using this mode permits DNSSEC downgrade attacks, as an attacker might be
|
|
able turn off DNSSEC validation on the system by inserting DNS replies in the
|
|
communication channel that result in a downgrade like this.
|
|
|
|
This event might be indication that the DNS server is indeed incompatible with
|
|
DNSSEC or that an attacker has successfully managed to stage such a downgrade
|
|
attack.
|
|
|
|
-- 1675d7f172174098b1108bf8c7dc8f5d
|
|
Subject: DNSSEC validation failed
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
Documentation: man:systemd-resolved.service(8)
|
|
|
|
A DNS query or resource record set failed DNSSEC validation. This is usually
|
|
indication that the communication channel used was tampered with.
|
|
|
|
-- 4d4408cfd0d144859184d1e65d7c8a65
|
|
Subject: A DNSSEC trust anchor has been revoked
|
|
Defined-By: systemd
|
|
Support: %SUPPORT_URL%
|
|
Documentation: man:systemd-resolved.service(8)
|
|
|
|
A DNSSEC trust anchor has been revoked. A new trust anchor has to be
|
|
configured, or the operating system needs to be updated, to provide an updated
|
|
DNSSEC trust anchor.
|