File manager - Edit - /home/u478019808/domains/bestandroidphones.store/public_html/static/img/logo/catalog.zip
Back
PK �v�Z�)z�" " systemd.zh_CN.catalognu �[��� # SPDX-License-Identifier: LGPL-2.1-or-later # # Copyright © 2015 Boyuan Yang # Message catalog for systemd's own messages # Simplified Chinese translation # 本 catalog 文档格式被记载在 # https://www.freedesktop.org/wiki/Software/systemd/catalog # 如需了解我们为什么做这些工作，请见 https://xkcd.com/1024/ -- f77379a8490b408bbe5f6940505a777b Subject: 日志已开始 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 系统日志进程已启动，已打开供写入的日志文件并准备好处理请求。 -- d93fb3c9c24d451a97cea615ce59c00b Subject: 日志已停止 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 系统日志进程已终止，并已关闭所有当前活动的日志文件。 -- a596d6fe7bfa4994828e72309e95d61e Subject: 由某个服务而来的消息已被抑制 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:journald.conf(5) 某个服务在一个时间周期内记录了太多消息。 从该服务而来的消息已被丢弃。 请注意只有由有问题的服务传来的消息被丢弃， 其它服务的消息不受影响。 可以在 /etc/systemd/journald.conf 中设定 RateLimitIntervalSec= 以及 RateLimitBurst = 的值以控制丢弃信息的限制。 请参见 journald.conf(5) 以了解详情。 -- e9bf28e6e834481bb6f48f548ad13606 Subject: 日志消息已遗失 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 因日志系统对内核消息的处理速度不够快， 部分信息已经遗失。 -- fc2e22bc6ee647b6b90729ab34a250b1 Subject: 进程 @COREDUMP_PID@ (@COREDUMP_COMM@) 核心已转储 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:core(5) 进程 @COREDUMP_PID@ (@COREDUMP_COMM@) 已崩溃并进行核心转储。 这通常意味着崩溃程序中存在编程错误，并应当将此错误向其开发者报告。 -- 8d45620c1a4348dbb17410da57c60c66 Subject: 一个新会话 @SESSION_ID@ 已为用户 @USER_ID@ 建立 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) 一个 ID 为 @SESSION_ID@ 的新会话已为用户 @USER_ID@ 建立。 该会话的首进程为 @LEADER@。 -- 3354939424b4456d9802ca8333ed424a Subject: 会话 @SESSION_ID@ 已终止 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) 一个 ID 为 @SESSION_ID@ 的会话已终止。 -- fcbefc5da23d428093f97c82a9290f7b Subject: 一个新的座位 @SEAT_ID@ 可用 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) 一个新的座位 @SEAT_ID@ 已被配置并已可用。 -- e7852bfe46784ed0accde04bc864c2d5 Subject: 座位 @SEAT_ID@ 已被移除 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) 座位 @SEAT_ID@ 已被移除并不再可用。 -- c7a787079b354eaaa9e77b371893cd27 Subject: 时间已变更 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 系统时钟已变更为1970年1月1日后 @REALTIME@ 微秒。 -- 45f82f4aef7a4bbf942ce861d1f20990 Subject: 时区变更为 @TIMEZONE@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 系统时区已变更为 @TIMEZONE@。 -- b07a249cd024414a82dd00cd181378ff Subject: 系统启动已完成 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 所有系统启动时需要的系统服务均已成功启动。 请注意这并不代表现在机器已经空闲，因为某些服务可能仍处于完成启动的过程中。 内核启动使用了 @KERNEL_USEC@ 毫秒。 初始内存盘启动使用了 @INITRD_USEC@ 毫秒。 用户空间启动使用了 @USERSPACE_USEC@ 毫秒。 -- 6bbd95ee977941e497c48be27c254128 Subject: 系统已进入 @SLEEP@ 睡眠状态 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 系统现已进入 @SLEEP@ 睡眠状态。 -- 8811e6df2a8e40f58a94cea26f8ebf14 Subject: 系统已离开 @SLEEP@ 睡眠状态 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 系统现已离开 @SLEEP@ 睡眠状态。 -- 98268866d1d54a499c4e98921d93bc40 Subject: 系统关机已开始 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 系统关机操作已初始化。 关机已开始，所有系统服务均已结束，所有文件系统已卸载。 -- 7d4958e842da4a758f6c1cdc7b36dcc5 Subject: @UNIT@ 单元已开始启动 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support @UNIT@ 单元已开始启动。 -- 39f53479d3a045ac8e11786248231fbf Subject: @UNIT@ 单元已结束启动 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support @UNIT@ 单元已结束启动。 启动结果为“@JOB_RESULT@”。 -- de5b426a63be47a7b6ac3eaac82e2f6f Subject: @UNIT@ 单元已开始停止操作 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support @UNIT@ 单元已开始停止操作。 -- 9d1aaa27d60140bd96365438aad20286 Subject: @UNIT@ 单元已结束停止操作 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support @UNIT@ 单元已结束停止操作。 -- be02cf6855d2428ba40df7e9d022f03d Subject: @UNIT@ 单元已失败 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support @UNIT@ 单元已失败。 结果为“@JOB_RESULT@”。 -- d34d037fff1847e6ae669a370e694725 Subject: @UNIT@ 单元已开始重新载入其配置 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support @UNIT@ 单元已开始重新载入其配置。 -- 7b05ebc668384222baa8881179cfda54 Subject: @UNIT@ 单元已结束配置重载入 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support @UNIT@ 单元已结束配置重载入操作。 结果为“@JOB_RESULT@”。 -- 641257651c1b4ec9a8624d7a40a9e1e7 Subject: 进程 @EXECUTABLE@ 无法执行 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 进程 @EXECUTABLE@ 无法被执行并已失败。 该进程返回的错误代码为 @ERRNO@。 -- 0027229ca0644181a76c4e92458afa2e Subject: 一个或更多消息无法被转发至 syslog Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 有一条或更多的消息无法被转发至与 journald 同时运行的 syslog 服务。 这通常意味着 syslog 实现无法跟上队列中消息进入的速度。 -- 1dee0369c7fc4736b7099b38ecb46ee7 Subject: 挂载点不为空 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 目录 @WHERE@ 被指定为挂载点（即 /etc/fstab 文件的第二栏，或 systemd 单元 文件的 Where= 字段），且该目录非空。 这并不会影响挂载行为，但该目录中先前已存在的文件将无法被访问。 如需查看这些文件，请手动将其下的文件系统挂载到另一个位置。 -- 24d8d4452573402496068381a6312df2 Subject: 一个虚拟机或容器已启动 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 虚拟机 @NAME@，以及其首进程 PID @LEADER@，已被启动并可被使用。 -- 58432bd3bace477cb514b56381b8a758 Subject: 一个虚拟机或容器已被终止 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 虚拟机 @NAME@，以及其首进程 PID @LEADER@，已被关闭并停止。 PK �v�Z#3�{� � dbus-broker-launch.catalognu �[��� -- 7fc63312330b479bb32e598d47cef1a8 Subject: Activation request failed due to missing unit Defined-By: dbus-broker Support: https://groups.google.com/forum/#!forum/bus1-devel systemd failed to activate the name @DBUS_BROKER_LAUNCH_SERVICE_NAME@ because the service @DBUS_BROKER_LAUNCH_SERVICE_UNIT@ could not be found. A possible reason for this is that @DBUS_BROKER_LAUNCH_SERVICE_UNIT@ is an alias to a disabled service. This is allowed by design, to give the administrator a way to disable name activation for a given service while still allowing it to be installed and potentially started in other ways. In order not to flood the logs, this message is only emitted once per name. -- ee9799dab1e24d81b7bee7759a543e1b Subject: Activation request failed due to masked unit Defined-By: dbus-broker Support: https://groups.google.com/forum/#!forum/bus1-devel systemd failed to activate the name @DBUS_BROKER_LAUNCH_SERVICE_NAME@ because the service @DBUS_BROKER_LAUNCH_SERVICE_UNIT@ was masked. It is a valid setup to mask units to disable them locally, but keep them installed. Therefore, this is not considered an error. If you want the service to be activatable via D-Bus, you must unmask the service. The systemd documentation contains more information on masked services. In order not to flood the logs, this message is only emitted once per name. -- f15d2347662d483ea9bcd8aa1a691d28 Subject: dbus-broker-launch received a SIGHUP Defined-By: dbus-broker Support: https://groups.google.com/forum/#!forum/bus1-devel The HUP signal was sent to the dbus-broker-launch process from PID @DBUS_BROKER_LAUNCH_SIGNAL_PID@, triggering a configuration reload. Note that SIGHUP is delivered asynchronously, so the caller doesn't know when the requested reload has completed. It is therefore recommended to use the org.freedekstop.DBus.ReloadConfig method call on the driver instead. -- c8c6cde1c488439aba371a664353d9d8 Subject: A configuration directory was written to Defined-By: dbus-broker Support: https://groups.google.com/forum/#!forum/bus1-devel A write was detected to one of the directories containing D-Bus configuration files, triggering a configuration reload. This functionality exists for backwards compatibility to pick up changes to D-Bus configuration without an explicit reolad request. Typically when installing or removing third-party software causes D-Bus configuration files to be added or removed. It is worth noting that this may cause partial configuration to be loaded in case dispatching this notification races with the writing of the configuration files. However, a future notification will then cause the configuration to be reladed again. -- 0ce0fa61d1a9433dabd67417f6b8e535 Subject: Failed to open service file Defined-By: dbus-broker Support: https://groups.google.com/forum/#!forum/bus1-devel A service file could not be opened for reading. For compatibility reasons the error is ignored and loading of the other service files continues. Failure to open the file file may be caused by for instance, a concurrent removal of the file or the file not being readable. -- 24dc708d9e6a4226a3efe2033bb744de Subject: Invalid service file Defined-By: dbus-broker Support: https://groups.google.com/forum/#!forum/bus1-devel A service file is a ini-type configuration file. It has one required section named [D-BUS Service]. The section contains the required key 'Name', which must be a valid D-Bus name that is unique across all service files. It also contains at least one of the two optional keys 'SystemdService' and 'Exec', as well as optionally the key 'User'. Exec must be a valid shell command and User must be a valid user on the system. A service file should be named after the D-Bus name it configures. That is a file containing Name=org.foo.bar1 should be named org.foo.bar1.service. For backwards compatibility, we only warn when files do not follow this convention when run as a user bus. The system bus considers this an error and ignores the service file. -- a0fa58cafd6f4f0c8d003d16ccf9e797 Subject: dbus-broker process exited Defined-By: dbus-broker Support: https://groups.google.com/forum/#!forum/bus1-devel The dbus-broker-launch process was notified that its child, dbus-broker exited. PK �v�ZC8~�P �P systemd.ru.catalognu �[��� # SPDX-License-Identifier: LGPL-2.1-or-later # # Copyright © 2013-2017 Sergey Ptashnick # Message catalog for systemd's own messages # Russian translation # Формат каталога сообщений описан по ссылке # https://www.freedesktop.org/wiki/Software/systemd/catalog # Перед каждым элементом в комментарии указан Subject исходного # сообщения (на английском). # Subject: The Journal has been started -- f77379a8490b408bbe5f6940505a777b Subject: Запущена служба журналирования Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Процесс, отвечающий за журналирование системных событий, успешно запустился, открыл для записи файлы журнала, и готов обрабатывать запросы. # Subject: The Journal has been stopped -- d93fb3c9c24d451a97cea615ce59c00b Subject: Служба журналирования остановлена Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Процесс, отвечающий за журналирование системных событий, завершил работу и закрыл все свои файлы. # Subject: Disk space used by the journal -- ec387f577b844b8fa948f33cad9a75e6 Subject: Место на диске, занятое журналом Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support @JOURNAL_NAME@ (@JOURNAL_PATH@) сейчас занимает @CURRENT_USE_PRETTY@. Максимальный разрешенный размер составляет @MAX_USE_PRETTY@. Оставляем свободными как минимум @DISK_KEEP_FREE_PRETTY@ (сейчас на диске свободно @DISK_AVAILABLE_PRETTY@). Таким образом, предел использования составляет @LIMIT_PRETTY@, из которых @AVAILABLE_PRETTY@ пока свободно. Ограничения на размер журнала настраиваются при помощи параметров SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= в файле /etc/systemd/journald.conf. Более подробные сведения вы можете получить на справочной странице journald.conf(5). # Subject: Messages from a service have been suppressed -- a596d6fe7bfa4994828e72309e95d61e Subject: Часть сообщений от службы пропущена Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:journald.conf(5) Служба отправила слишком много сообщений за короткий промежуток времени. Часть сообщений была пропущена. Обратите внимание, что были пропущены сообщения только от этой службы, сообщения других служб не затронуты. Предел, после которого служба журнала начинает игнорировать сообщения, настраивается параметрами RateLimitIntervalSec= и RateLimitBurst= в файле /etc/systemd/journald.conf. Подробности смотрите на странице руководства journald.conf(5). # Subject: Journal messages have been missed -- e9bf28e6e834481bb6f48f548ad13606 Subject: Часть сообщений ядра пропущена Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Часть сообщений, поступивших от ядра, была потеряна, так как служба журналирования не успела их обработать. # Subject: Process @COREDUMP_PID@ (@COREDUMP_COMM@) dumped core -- fc2e22bc6ee647b6b90729ab34a250b1 Subject: Процесс @COREDUMP_PID@ (@COREDUMP_COMM@) сбросил дамп памяти Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:core(5) Процесс @COREDUMP_PID@ (@COREDUMP_COMM@) завершился из-за критической ошибки. Записан дамп памяти. Вероятно, это произошло из-за ошибки, допущенной в коде программы. Рекомендуется сообщить её разработчикам о возникшей проблеме. # Subject: Core file was truncated to @SIZE_LIMIT@ bytes -- 5aadd8e954dc4b1a8c954d63fd9e1137 Subject: Файл с дампом памяти был урезан до @SIZE_LIMIT@ байт Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:coredump.conf(5) Объем памяти процесса превысил ограничения на размер дампа, установленные для systemd-coredump(8). Записаны только первые @SIZE_LIMIT@ байт. Не исключено, что этот дамп еще пригоден для анализа, хотя инструменты для анализа дампов (например, gdb(1)) могут выдать предупреждение, что файл был урезан. # Subject: A new session @SESSION_ID@ has been created for user @USER_ID@ -- 8d45620c1a4348dbb17410da57c60c66 Subject: Для пользователя @USER_ID@ создан новый сеанс @SESSION_ID@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Для пользователя @USER_ID@ создан новый сеанс с идентификатором @SESSION_ID@. Главный процесс нового сеанса имеет индентификатор @LEADER@. # Subject: A session @SESSION_ID@ has been terminated -- 3354939424b4456d9802ca8333ed424a Subject: Сеанс @SESSION_ID@ завершен Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Сеанс с идентификатором @SESSION_ID@ завершился. # Subject: A new seat @SEAT_ID@ is now available -- fcbefc5da23d428093f97c82a9290f7b Subject: Добавлено новое рабочее место @SEAT_ID@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Новое рабочее место (seat) @SEAT_ID@ полностью настроено и готово к использованию. # Subject: A seat @SEAT_ID@ has now been removed -- e7852bfe46784ed0accde04bc864c2d5 Subject: Рабочее место @SEAT_ID@ отключено Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Рабочее место (seat) @SEAT_ID@ было отключено. # Subject: Time change -- c7a787079b354eaaa9e77b371893cd27 Subject: Переведены системные часы Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Системные часы были переведены. Сейчас они показывают @REALTIME@ микросекунд с момента 00:00:00 1 января 1970 года. # Subject: Time zone change to @TIMEZONE@ -- 45f82f4aef7a4bbf942ce861d1f20990 Subject: Часовой пояс изменен на @TIMEZONE@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Системный часовой пояс был изменен. Новое значение: @TIMEZONE@. # Subject: System start-up is now complete -- b07a249cd024414a82dd00cd181378ff Subject: Запуск системы завершен Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Все системные службы, запуск которых предписан настройками, были запущены. Впрочем, это ещё не означает, что система в данный момент ничем не занята, так как некоторые службы могут продолжать инициализацию даже после того, как отчитались о своем запуске. Запуск ядра занял @KERNEL_USEC@ микросекунд. Процессы начального RAM-диска (initrd) отработали за @INITRD_USEC@ микросекунд. Запуск системных служб занял @USERSPACE_USEC@ микросекунд. # Subject: User manager start-up is now complete -- eed00a68ffd84e31882105fd973abdd1 Subject: Завершен запуск менеджера пользовательского сеанса Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Менеджер пользовательского сеанса для пользователя с идентификатором @_UID@ был запущен. Все службы, стоявшие в очереди на запуск, также были запущены. Тем не менее, прочие службы могут все еще находиться в процессе запуска, либо могут быть запущены позднее. Запуск менеджера занял @USERSPACE_USEC@ микросекунд. # Subject: System sleep state @SLEEP@ entered -- 6bbd95ee977941e497c48be27c254128 Subject: Система перешла в состояние сна (@SLEEP@) Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Система была переведена в состояние сна (@SLEEP@). # Subject: System sleep state @SLEEP@ left -- 8811e6df2a8e40f58a94cea26f8ebf14 Subject: Система вышла из состояния сна (@SLEEP@) Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Система была выведена из состояния сна (@SLEEP@). # Subject: System shutdown initiated -- 98268866d1d54a499c4e98921d93bc40 Subject: Подготовка системы к выключению Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Начат процесс подготовки к выключению компьютера. Останавливаются все системные службы, отмонтируются все файловые системы. # Subject: Unit @UNIT@ has begun with start-up -- 7d4958e842da4a758f6c1cdc7b36dcc5 Subject: Начинается запуск юнита @UNIT@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Начат процесс запуска юнита @UNIT@. # Subject: Unit @UNIT@ has finished start-up -- 39f53479d3a045ac8e11786248231fbf Subject: Запуск юнита @UNIT@ завершен Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Процесс запуска юнита @UNIT@ был завершен. Результат: @JOB_RESULT@. # Subject: Unit @UNIT@ has begun shutting down -- de5b426a63be47a7b6ac3eaac82e2f6f Subject: Начинается остановка юнита @UNIT@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Начат процесс остановки юнита @UNIT@. # Subject: Unit @UNIT@ has finished shutting down -- 9d1aaa27d60140bd96365438aad20286 Subject: Завершена остановка юнита @UNIT@. Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Процесс остановки юнита @UNIT@ был завершен. # Subject: Unit @UNIT@ has failed -- be02cf6855d2428ba40df7e9d022f03d Subject: Ошибка юнита @UNIT@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Произошел сбой юнита @UNIT@. Результат: @JOB_RESULT@. # Subject: Unit @UNIT@ has begun with reloading its configuration -- d34d037fff1847e6ae669a370e694725 Subject: Юнит @UNIT@ начал перечитывать свои настройки Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Юнит @UNIT@ начал процесс перечитывания своей конфигурации. # Subject: Unit @UNIT@ has finished reloading its configuration -- 7b05ebc668384222baa8881179cfda54 Subject: Юнит @UNIT@ завершил перечитывание своих настроек Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Юнит @UNIT@ завершил процесс перечитывания своей конфигурации. Результат: @JOB_RESULT@. # Subject: Process @EXECUTABLE@ could not be executed -- 641257651c1b4ec9a8624d7a40a9e1e7 Subject: Не удалось запустить процесс @EXECUTABLE@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Сбой: не удалось запустить процесс @EXECUTABLE@. Код ошибки: @ERRNO@. # Subject: One or more messages could not be forwarded to syslog -- 0027229ca0644181a76c4e92458afa2e Subject: Часть сообщений не удалось передать процессу syslog Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Не удалось передать некоторые сообщения демону системного лога (syslog), дублирующему работу службы системного журнала. Скорее всего, причина в том, что используемая реализация syslog не успевает обрабатывать сообщения с достаточной скоростью. # Subject: Mount point is not empty -- 1dee0369c7fc4736b7099b38ecb46ee7 Subject: Каталог, являющийся точкой монтирования, не пуст Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Каталог @WHERE@, который был указан в качестве точки монтирования (во втором столбце файла /etc/fstab, либо в параметре Where= файла конфигурации юнита), не является пустым. Это никак не мешает монтированию, однако ранее находившиеся в нем файлы будут недоступны. Чтобы получить к ним доступ, вы можете вручную перемонтировать эту файловую систему в другую точку. # Subject: A virtual machine or container has been started -- 24d8d4452573402496068381a6312df2 Subject: Запущена виртуальная машина/контейнер Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Виртуальная машина @NAME@ (идентификатор главного процесса: @LEADER@) запущена и готова к работе. # Subject: A virtual machine or container has been terminated -- 58432bd3bace477cb514b56381b8a758 Subject: Остановлена виртуальная машина/контейнер Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Виртуальная машина @NAME@ (идентификатор главного процесса: @LEADER@) выключена. # Subject: DNSSEC mode has been turned off, as server doesn't support it -- 36db2dfa5a9045e1bd4af5f93e1cf057 Subject: Механизм DNSSEC был отключен, так как DNS-сервер его не поддерживает Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) resolved.conf(5) Служба разрешения имен хостов (systemd-resolved.service) определила, что указанный в настойках DNS-сервер не поддерживает технологию DNSSEC, и автоматически отключила DNSSEC-проверки. Данное событие возникает, если в файле resolved.conf указан параметр DNSSEC=allow-downgrade, и вышестоящий DNS-сервер не поддерживает DNSSEC. Обратите внимание, что режим allow-downgrade допускает возможность атаки "DNSSEC downgrade", в ходе которой атакующий хакер блокирует проверки DNSSEC путем отправки ложных сообщений от имени DNS-сервера. Возникновение данного события может свидетельствовать как о том, что ваш DNS-сервер не поддерживает DNSSEC, так и о том, что некий хакер успешно провел против вас атаку, направленную на блокировку DNSSEC-проверок. # Subject: DNSSEC validation failed -- 1675d7f172174098b1108bf8c7dc8f5d Subject: Проверка DNSSEC провалена Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) DNS-запрос или отдельная ресурсная запись не прошла проверку DNSSEC. Как правило, это свидетельствует о постороннем вмешательстве в канал связи. # Subject: A DNSSEC trust anchor has been revoked -- 4d4408cfd0d144859184d1e65d7c8a65 Subject: Открытый ключ DNSSEC был отозван Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) Открытый ключ (trust ahcnor) DNSSEC был отозван. Необходимо настроить новый открытый ключ, либо обновить систему, чтобы получить обновленный открытый ключ. # Subject: Automatic restarting of a unit has been scheduled -- 5eb03494b6584870a536b337290809b3 Subject: Назначен автоматический перезапуск юнита Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Назначен автоматический перезапуск юнита @UNIT@, так как для него был задан параметр Restart=. # Subject: Resources consumed by unit runtime -- ae8f7b866b0347b9af31fe1c80b127c0 Subject: Потребленные юнитом ресурсы Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Юнит @UNIT@ завершен. Приводится статистика по потребленным им ресурсам. # Subject: The system is configured in a way that might cause problems -- 50876a9db00f4c40bde1a2ad381c3a1b Subject: Выявлены потенциальные проблемы в конфигурации системы Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Перечень всех возможных меток, указывающих на проблемы конфигурации: - "split-usr" — каталог /usr расположен на отдельной файловой системе, которая не была смонтирована на момент запуска systemd - "cgroups-missing" — ядро собрано без поддержки контрольных групп, либо отсутствуют права для доступа к интерфейсным файлам контрольных групп - "var-run-bad" — /var/run не является символьной ссылкой на /run - "overflowuid-not-65534" — используемый ядром UID для "неизвестных" пользователей (применяется в NFS и пространствах имен пользователей) не равен 65534 - "overflowgid-not-65534" — используемый ядром GID для "неизвестных" пользователей (применяется в NFS и пространствах имен пользователей) не равен 65534 В вашей системе присутствуют следующие проблемы: @TAINT@. PK �v�ZG�U6�V �V systemd.pl.catalognu �[��� # SPDX-License-Identifier: LGPL-2.1-or-later # Message catalog for systemd's own messages # Polish translation # The catalog format is documented on # https://www.freedesktop.org/wiki/Software/systemd/catalog # For an explanation why we do all this, see https://xkcd.com/1024/ -- f77379a8490b408bbe5f6940505a777b Subject: Uruchomiono dziennik Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Systemowy proces dziennika został uruchomiony, otworzył pliki dziennika do zapisu i jest gotowy do przetwarzania żądań. -- d93fb3c9c24d451a97cea615ce59c00b Subject: Zatrzymano dziennik Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Systemowy proces dziennika został wyłączony i zamknął wszystkie obecnie aktywne pliki dziennika. -- ec387f577b844b8fa948f33cad9a75e6 Subject: Miejsce na dysku używane przez dziennik Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support @JOURNAL_NAME@ (@JOURNAL_PATH@) obecnie używa @CURRENT_USE_PRETTY@. Maksymalnie może używać @MAX_USE_PRETTY@. Zostawianie co najmniej @DISK_KEEP_FREE_PRETTY@ wolnego (z obecnie dostępnego @DISK_AVAILABLE_PRETTY@ miejsca na dysku). Wymuszone ograniczenie użycia wynosi więc @LIMIT_PRETTY@, z czego @AVAILABLE_PRETTY@ jest nadal dostępne. Ograniczenia kontrolujące ilość miejsca na dysku używanego przez dziennik można konfigurować za pomocą ustawień SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= w pliku /etc/systemd/journald.conf. Strona journald.conf(5) zawiera więcej informacji. -- a596d6fe7bfa4994828e72309e95d61e Subject: Ograniczono komunikaty z usługi Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:journald.conf(5) Usługa zapisała za dużo komunikatów w określonym czasie. Komunikaty z usługi zostały pominięte. Proszę zauważyć, że tylko komunikaty z danej usługi zostały pominięte. Nie ma to wpływu na komunikaty innych usług. Ograniczenia kontrolujące pomijanie komunikatów mogą być konfigurowane za pomocą opcji RateLimitIntervalSec= i RateLimitBurst= w pliku /etc/systemd/journald.conf lub LogRateLimitIntervalSec= i LogRateLimitBurst= w pliku jednostki. Strony journald.conf(5) i systemd.exec(5) zawierają więcej informacji. -- e9bf28e6e834481bb6f48f548ad13606 Subject: Utracono komunikaty dziennika Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Komunikaty jądra zostały utracone, ponieważ system dziennika nie mógł przetworzyć ich odpowiednio szybko. -- fc2e22bc6ee647b6b90729ab34a250b1 Subject: Proces @COREDUMP_PID@ (@COREDUMP_COMM@) zrzucił plik core Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:core(5) Proces @COREDUMP_PID@ (@COREDUMP_COMM@) uległ awarii i zrzucił plik core. Zwykle wskazuje to na błąd programistyczny w danym programie i powinno zostać zgłoszone jego producentowi jako błąd. -- 5aadd8e954dc4b1a8c954d63fd9e1137 Subject: Plik core został skrócony do @SIZE_LIMIT@ B. Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:coredump.conf(5) Proces miał więcej zmapowanej pamięci niż maksimum dla przetwarzania i miejsca skonfigurowane przez systemd-coredump(8). Tylko pierwsze @SIZE_LIMIT@ B zostało zapisanych. Ten plik core może nadal być używalny, ale narzędzia typu gdb(1) będą ostrzegały o skróceniu pliku. -- 8d45620c1a4348dbb17410da57c60c66 Subject: Utworzono nową sesję @SESSION_ID@ dla użytkownika @USER_ID@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Nowa sesja o identyfikatorze @SESSION_ID@ została utworzona dla użytkownika @USER_ID@. Proces prowadzący sesji: @LEADER@. -- 3354939424b4456d9802ca8333ed424a Subject: Zakończono sesję @SESSION_ID@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Sesja o identyfikatorze @SESSION_ID@ została zakończona. -- fcbefc5da23d428093f97c82a9290f7b Subject: Dostępne jest nowe stanowisko @SEAT_ID@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Nowe stanowisko @SEAT_ID@ zostało skonfigurowane i jest teraz dostępne. -- e7852bfe46784ed0accde04bc864c2d5 Subject: Usunięto stanowisko @SEAT_ID@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Stanowisko @SEAT_ID@ zostało usunięte i nie jest już dostępne. -- c7a787079b354eaaa9e77b371893cd27 Subject: Zmiana czasu Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Zegar systemowy został zmieniony na @REALTIME@ μs po 1 stycznia 1970. -- 45f82f4aef7a4bbf942ce861d1f20990 Subject: Zmiana strefy czasowej na @TIMEZONE@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Systemowa strefa czasowa została zmieniona na @TIMEZONE@. -- b07a249cd024414a82dd00cd181378ff Subject: Ukończono uruchamianie systemu Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Wszystkie usługi systemowe obowiązkowo zakolejkowane do włączenia podczas uruchamiania systemu zostały uruchomione. Proszę zauważyć, że nie oznacza to, że komputer jest bezczynny, jako że usługi mogą wciąż kończyć proces uruchamiania. Uruchamianie jądra zajęło @KERNEL_USEC@ μs. Uruchamianie początkowego dysku RAM zajęło @INITRD_USEC@ μs. Uruchamianie przestrzeni użytkownika zajęło @USERSPACE_USEC@ μs. -- eed00a68ffd84e31882105fd973abdd1 Subject: Ukończono uruchamianie menedżera użytkownika Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Wystąpienie menedżera dla użytkownika @_UID@ zostało uruchomione. Wszystkie usługi zakolejkowane do włączenia zostały uruchomione. Proszę zauważyć, że inne usługi mogą być nadal uruchamiane lub zostać uruchomione później. Uruchamianie menedżera zajęło @USERSPACE_USEC@ μs. -- 6bbd95ee977941e497c48be27c254128 Subject: Przejście do stanu uśpienia @SLEEP@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support System przeszedł do stanu uśpienia @SLEEP@. -- 8811e6df2a8e40f58a94cea26f8ebf14 Subject: Wyjście ze stanu uśpienia @SLEEP@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support System wyszedł ze stanu uśpienia @SLEEP@. -- 98268866d1d54a499c4e98921d93bc40 Subject: Zainicjowano wyłączenie systemu Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Zainicjowano wyłączenie systemu. Wyłączenie zostało rozpoczęte i wszystkie usługi systemowe zostały zakończone, a wszystkie systemy plików odmontowane. -- c14aaf76ec284a5fa1f105f88dfb061c Subject: Zainicjowano przywrócenie danych fabrycznych systemu Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Zainicjowano przywrócenie danych fabrycznych systemu. Dokładne działanie, jakie zostanie wykonane jest określone przez implementację, ale zwykle powoduje przywrócenie stanu i konfiguracji systemu do domyślnych wartości producenta. -- 7d4958e842da4a758f6c1cdc7b36dcc5 Subject: Rozpoczęto wykonywanie zadania uruchamiania dla jednostki @UNIT@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Rozpoczęto wykonywanie zadania uruchamiania dla jednostki @UNIT@. Identyfikator zadania: @JOB_ID@. -- 39f53479d3a045ac8e11786248231fbf Subject: Pomyślnie ukończono zadanie uruchamiania dla jednostki @UNIT@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Pomyślnie ukończono zadanie uruchamiania dla jednostki @UNIT@. Identyfikator zadania: @JOB_ID@. -- be02cf6855d2428ba40df7e9d022f03d Subject: Zadanie uruchamiania dla jednostki @UNIT@ się nie powiodło Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Zadanie uruchamiania dla jednostki @UNIT@ zostało ukończone z niepowodzeniem. Identyfikator zadania: @JOB_ID@, wynik zadania: @JOB_RESULT@. -- de5b426a63be47a7b6ac3eaac82e2f6f Subject: Rozpoczęto wykonywanie zadania zatrzymania dla jednostki @UNIT@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Rozpoczęto wykonywanie zadania zatrzymania dla jednostki @UNIT@. Identyfikator zadania: @JOB_ID@. -- 9d1aaa27d60140bd96365438aad20286 Subject: Ukończono zadanie zatrzymania dla jednostki @UNIT@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Ukończono zadanie zatrzymania dla jednostki @UNIT@. Identyfikator zadania: @JOB_ID@, wynik zadania: @JOB_RESULT@. -- d34d037fff1847e6ae669a370e694725 Subject: Rozpoczęto wykonywanie zadania ponownego wczytania dla jednostki @UNIT@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Rozpoczęto wykonywanie zadania ponownego wczytania dla jednostki @UNIT@. Identyfikator zadania: @JOB_ID@. -- 7b05ebc668384222baa8881179cfda54 Subject: Ukończono zadanie ponownego wczytania dla jednostki @UNIT@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Ukończono zadanie ponownego wczytania dla jednostki @UNIT@. Identyfikator zadania: @JOB_ID@, wynik zadania: @JOB_RESULT@. -- 641257651c1b4ec9a8624d7a40a9e1e7 Subject: Nie można wykonać procesu @EXECUTABLE@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Proces @EXECUTABLE@ nie mógł zostać wykonany i się nie powiódł. Numer błędu zwrócony przez ten proces: @ERRNO@. -- 0027229ca0644181a76c4e92458afa2e Subject: Nie można przekazać jednego lub więcej komunikatów do syslog Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Jeden lub więcej komunikatów nie może zostać przekazanych do usługi syslog uruchomionej obok journald. Zwykle oznacza to, że implementacja syslog nie jest w stanie nadążyć za prędkością kolejki komunikatów. -- 1dee0369c7fc4736b7099b38ecb46ee7 Subject: Punkt montowania nie jest pusty Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Katalog @WHERE@ został podany jako punkt montowania (drugie pole w pliku /etc/fstab lub pole Where= w pliku jednostki systemd) i nie jest pusty. Nie wpływa to na montowanie, ale wcześniej istniejące pliki w tym katalogu stają się niedostępne. Aby zobaczyć te pliki, proszę ręcznie zamontować system plików w innym położeniu. -- 24d8d4452573402496068381a6312df2 Subject: Uruchomiono maszynę wirtualną lub kontener Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Maszyna wirtualna @NAME@ (PID prowadzący @LEADER@) została uruchomiona i jest gotowa do użycia. -- 58432bd3bace477cb514b56381b8a758 Subject: Zakończono maszynę wirtualną lub kontener Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Maszyna wirtualna @NAME@ (PID prowadzący @LEADER@) została wyłączona. -- 36db2dfa5a9045e1bd4af5f93e1cf057 Subject: Wyłączono tryb DNSSEC, ponieważ serwer go nie obsługuje Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) Documentation: man:resolved.conf(5) Usługa resolver (systemd-resolved.service) wykryła, że skonfigurowany serwer DNS nie obsługuje DNSSEC, w wyniku czego walidacja DNSSEC została wyłączona. To zdarzenie będzie miało miejsce, jeśli skonfigurowano DNSSEC=allow-downgrade w pliku resolved.conf, a skonfigurowany serwer DNS jest niezgodny z DNSSEC. Proszę zauważyć, że używanie tego trybu umożliwia ataki wyłączające DNSSEC, ponieważ atakujący będzie mógł wyłączyć walidację DNSSEC na komputerze przez umieszczenie odpowiednich odpowiedzi DNS w kanale komunikacji. To zdarzenie może wskazywać, że serwer DNS jest faktycznie niezgodny z DNSSEC, albo że atakującemu udało się upozorować atak tego typu. -- 1675d7f172174098b1108bf8c7dc8f5d Subject: Walidacja DNSSEC się nie powiodła Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) Zapytanie DNS lub ustawiony wpis zasobu nie przeszedł walidacji DNSSEC. Zwykle wskazuje to, że ktoś manipulował używanym kanałem komunikacji. -- 4d4408cfd0d144859184d1e65d7c8a65 Subject: Unieważniono kotwicę zaufania DNSSEC Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) Kotwica zaufania DNSSEC została unieważniona. Należy skonfigurować nową, albo system operacyjny musi zostać zaktualizowany, aby dostarczyć zaktualizowaną kotwicę zaufania DNSSEC. -- 5eb03494b6584870a536b337290809b3 Subject: Zaplanowano automatyczne ponowne uruchamianie jednostki Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support W wyniki skonfigurowania ustawienia Restart= zaplanowano automatyczne ponowne uruchamianie jednostki @UNIT@. -- ae8f7b866b0347b9af31fe1c80b127c0 Subject: Zasoby zużyte przez uruchomienie jednostki Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Jednostka @UNIT@ została ukończona, zużywając wskazane zasoby. -- 7ad2d189f7e94e70a38c781354912448 Subject: Jednostka się powiodła Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Jednostka @UNIT@ pomyślnie przeszła do stanu „dead” (martwego). -- 0e4284a0caca4bfc81c0bb6786972673 Subject: Pominięto jednostkę Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Jednostka @UNIT@ została pominięta z powodu niepowodzenia polecenia ExecCondition=, i przeszła do stanu „dead” (martwego) z wynikiem „@UNIT_RESULT@”. -- d9b373ed55a64feb8242e02dbe79a49c Subject: Jednostka się nie powiodła Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Jednostka @UNIT@ przeszła do stanu „failed” (niepowodzenia) z wynikiem „@UNIT_RESULT@”. -- 98e322203f7a4ed290d09fe03c09fe15 Subject: Proces jednostki zakończył działanie Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Proces @COMMAND@= należący do jednostki @UNIT@ zakończył działanie. Kod wyjścia procesu: „@EXIT_CODE@”, jego stan wyjścia: @EXIT_STATUS@. -- 50876a9db00f4c40bde1a2ad381c3a1b Subject: System jest skonfigurowany w sposób, który może powodować problemy Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Możliwe są następujące „etykiety”: • „split-usr” — /usr jest oddzielnym systemem plików, który nie był zamontowany w czasie uruchomienia systemd, • „cgroups-missing” — jądro zostało skompilowane bez obsługi cgroups lub dostęp do oczekiwanych plików interfejsu jest ograniczony, • „var-run-bad” — /var/run nie jest dowiązaniem symbolicznym do /run, • „overflowuid-not-65534” — identyfikator użytkownika dla „nieznanych” użytkowników (przy wykorzystaniu przestrzeni nazw użytkowników lub NFS) nie wynosi 65534, • „overflowgid-not-65534” — identyfikator grupy dla „nieznanych” użytkowników (przy wykorzystaniu przestrzeni nazw użytkowników lub NFS) nie wynosi 65534. Obecny system ma etykietę „@TAINT@”. -- fe6faa94e7774663a0da52717891d8ef Subject: Proces jednostki @UNIT@ został zakończony przez OOM Killer Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Proces jednostki @UNIT został zakończony przez mechanizm kończenia procesów przy braku pamięci (OOM) jądra Linux. Zwykle wskazuje to, że system ma mało pamięci i należało ją zwolnić. Proces powiązany z jednostką @UNIT@ został uznany za najlepszy do zakończenia i jądro wymusiło zakończenie jego działania. Proszę zauważyć, że brak pamięci mógł nie zostać spowodowany przez jednostkę @UNIT@. -- b61fdac612e94b9182285b998843061f Subject: Przyjmowanie nazwy użytkownika/grupy @USER_GROUP_NAME@, która nie zgadza się ze ścisłymi regułami nazw użytkowników/grup. Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: https://systemd.io/USER_NAMES Podano nazwę użytkownika/grupy @USER_GROUP_NAME@, co zostało przyjęte zgodnie z rozluźnionymi regułami nazw użytkowników/grup, ale nie spełnia ścisłych reguł. Ścisłe reguły nazw użytkowników/grup zapisane jako wyrażenie regularne to: ^[a-zA-Z_][a-zA-Z0-9_-]{0,30}$ Rozluźnione reguły nazw użytkowników/grup przyjmują wszystkie nazwy, oprócz pustego ciągu, nazw zawierających bajty NUL, znaki kontrolne, dwukropki lub ukośniki, nazw niebędących prawidłowym tekstem UTF-8, nazw z początkową lub końcową spacją, ciągów „.” lub „..”, ciągów zawierających tylko cyfry lub ciągów zaczynających się myślnikiem i zawierających oprócz niego tylko cyfry. -- 1b3bb94037f04bbf81028e135a12d293 Subject: Utworzenie prawidłowej nazwy jednostki ze ścieżki „@MOUNT_POINT@” się nie powiodło. Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Następująca ścieżka do punktu montowania nie może zostać przekonwertowana na prawidłową nazwę jednostki .mount: @MOUNT_POINT@ Zwykle oznacza to, że ścieżka do punktu montowania jest dłuższa niż dozwolona dla prawidłowych nazw jednostek. systemd dynamicznie syntetyzuje jednostki .mount dla wszystkich punktów montowania pojawiających się na komputerze. Stosowany do tego jest prosty algorytm: używana jest bezwzględna nazwa ścieżki ze wszystkimi znakami „/” zastąpionymi znakami „-” (początkowy jest usuwany). Co więcej, wszystkie niealfanumeryczne znaki (a także „:”, „-”, „_”, „.”, „\”) są zastępowane „\xNN”, gdzie „NN” jest szesnastkowym kodem znaki. Na końcu dołączany jest przyrostek „.mount”. Wynikowy ciąg musi mieć poniżej 256 znaków długości, aby był prawidłową nazwą jednostki. To ograniczenie obowiązuje, aby wszystkie nazwy jednostek mogły być używane także jako nazwy plików. Jeśli punkt montowania — po zastosowaniu algorytmu — jest dłuższy niż to ograniczenie, to nie może zostać zmapowany do jednostki. W takim przypadku systemd nie zsyntetyzuje jednostki i nie może być używany do zarządzania punktem montowania. Nie pojawi się w tabeli jednostek menedżera usług, przez co nie zostanie także bezpiecznie i automatycznie zdjęty podczas wyłączania komputera. Zasadniczo zalecane jest unikanie takich za długich ścieżek do punktów montowania, a jeśli są używane mimo to, zarządzanie nimi niezależnie od systemd, tzn. stawianie ich i automatyczne zdejmowanie podczas wyłączania komputera przez inne oprogramowanie. -- b480325f9c394a7b802c231e51a2752c Subject: Skonfigurowany jest szczególny użytkownik @OFFENDING_USER@, jest to niebezpieczne! Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: https://systemd.io/UIDS-GIDS Jednostka @UNIT@ jest skonfigurowana do używania User=@OFFENDING_USER@. Nie jest to bezpieczne. Głównym zastosowaniem użytkownika @OFFENDING_USER@ w linuksowych systemach operacyjnych jest bycie właścicielem plików, których nie można w inny sposób zmapować do żadnego lokalnego użytkownika. Jest używany między innymi przez klienta NFS i przestrzenie nazw użytkowników Linuksa. Wykonywanie procesów jednostki pod tożsamością tego użytkownika może spowodować, że będą one miały dostęp do odczytu, a może nawet do zapisu, plików, których nie można zmapować w inny sposób. Mocno zalecane jest unikanie wykonywania usług pod tą tożsamością użytkownika, zwłaszcza na komputerach używających NFS lub mających kontenery. Należy przydzielić identyfikator użytkownika dla tej konkretnej usługi, statycznie przez systemd-sysusers lub dynamicznie przez ustawienie usługi DynamicUser=. -- 1c0454c1bd2241e0ac6fefb4bc631433 Subject: Usługa systemd-udev-settle.service jest przestarzała. Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Użycie jednostki usługi systemd „systemd-udev-settle.service” jest przestarzałe. Wstawia ona sztuczne opóźnienie do procesu uruchamiania bez dostarczania gwarancji, które były oczekiwane przez pozostałe podsystemy. Korzystanie z tej usługi może prowadzić do hazardów, i zasadniczo jest błędem. W przeszłości zadaniem tej usługi było oczekiwanie, aż wszystkie urządzenia komputera zostaną w pełni wykryte i zainicjowane, opóźniając uruchamianie do ukończenia tego etapu. Jednakże, współczesne komputery i urządzenia na ogół nie działają już w ten sposób, tylko mogą pojawić się w dowolnej chwili i zająć dowolny czas na wykrycie i inicjację. Z tego powodu, w ogólnym przypadku, nie jest już możliwe poprawne opóźnienie uruchamiania do przetworzenia „wszystkich urządzeń”, ponieważ nie jest jasne, co znaczy „wszystkie urządzenia” i kiedy zostały odnalezione. Dotyczy to zwłaszcza urządzeń podłączonych przez USB lub sieć. Nowoczesne oprogramowanie wymagające określonego sprzętu (takiego jak urządzenie sieciowe lub urządzenie blokowe) do działania powinno oczekiwać tylko na pojawienie się danego urządzenia, a w przeciwnym razie działać asynchronicznie, inicjując urządzenia, kiedy te pojawiają się w trakcie uruchamiania i w trakcie działania systemu bez opóźniania procesu uruchamiania. Jest to wada danego oprogramowania, jeśli nie działa ono w ten sposób i nadal wciąga usługę systemd-udev-settle.service do procesu uruchamiania. Prosimy zgłosić błąd w następujących jednostkach z prośbą o ich aktualizację tak, aby działały w sposób dynamiczny bez zależności od usługi systemd-udev-settle.service: @OFFENDING_UNITS@ -- 7c8a41f37b764941a0e1780b1be2f037 Subject: Początkowa synchronizacja zegara Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Po raz pierwszy podczas obecnego uruchomienia uzyskano synchronizację NTP i zainicjowano regulację lokalnego zegara systemowego. PK �v�Z~����4 �4 systemd.fr.catalognu �[��� # SPDX-License-Identifier: LGPL-2.1-or-later # # Copyright © 2013-2016 Sylvain Plantefève # Message catalog for systemd's own messages # French translation # Le format du catalogue de messages est décrit (en anglais) içi : # https://www.freedesktop.org/wiki/Software/systemd/catalog -- f77379a8490b408bbe5f6940505a777b Subject: Le journal a été démarré Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Le processus du journal système a démarré, ouvert ses fichiers en écriture et est prêt à traiter les requêtes. -- d93fb3c9c24d451a97cea615ce59c00b Subject: Le journal a été arrêté Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Le processus du journal système a été arrêté et tous ses fichiers actifs ont été fermés. -- ec387f577b844b8fa948f33cad9a75e6 Subject: Espace disque utilisé par le journal Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:journald.conf(5) @JOURNAL_NAME@ (@JOURNAL_PATH@) utilise actuellement @CURRENT_USE_PRETTY@. Le maximum autorisé est défini à @MAX_USE_PRETTY@. Au moins @DISK_KEEP_FREE_PRETTY@ doivent être laissés libres (sur @DISK_AVAILABLE_PRETTY@ d'espace disque actuellement libre). La limite appliquée est donc @LIMIT_PRETTY@, dont @AVAILABLE_PRETTY@ sont toujours disponibles. Les limites définissant la quantité d'espace disque que peut utiliser le journal peuvent être configurées avec les paramètres SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= dans le fichier /etc/systemd/journald.conf. Voir journald.conf(5) pour plus de détails. -- a596d6fe7bfa4994828e72309e95d61e Subject: Des messages d'un service ont été supprimés Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:journald.conf(5) Un service a essayé d'enregistrer un trop grand nombre de messages sur un intervalle de temps donné. Des messages de ce service ont été évincés. Notez que seuls des messages de ce service ont été évincés, les messages des autres services ne sont pas affectés. Les limites définissant ce comportement peuvent être configurées avec les paramètres RateLimitIntervalSec= et RateLimitBurst= dans le fichier /etc/systemd/journald.conf. Voir journald.conf(5) pour plus de détails. -- e9bf28e6e834481bb6f48f548ad13606 Subject: Des messages du journal ont été manqués Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Des messages du noyau ont été manqués car le journal système n'a pas été capable de les traiter suffisamment vite. -- fc2e22bc6ee647b6b90729ab34a250b1 Subject: Le processus @COREDUMP_PID@ (@COREDUMP_COMM@) a généré un fichier « core » Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:core(5) Le processus @COREDUMP_PID@ (@COREDUMP_COMM@) a planté et généré un fichier « core ». Cela indique généralement une erreur de programmation dans le programme incriminé, et cela devrait être notifié à son concepteur comme un défaut (bug). -- 8d45620c1a4348dbb17410da57c60c66 Subject: Une nouvelle session @SESSION_ID@ a été créée pour l'utilisateur @USER_ID@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Une nouvelle session a été créée pour l'utilisateur @USER_ID@ avec l'identifiant (ID) @SESSION_ID@. Le processus maître de la session est @LEADER@. -- 3354939424b4456d9802ca8333ed424a Subject: La session @SESSION_ID@ s'est terminée Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) La session d'identifiant (ID) @SESSION_ID@ s'est terminée. -- fcbefc5da23d428093f97c82a9290f7b Subject: Un nouveau poste (seat) @SEAT_ID@ est disponible Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Un nouveau poste (seat) @SEAT_ID@ a été configuré et est maintenant disponible. -- e7852bfe46784ed0accde04bc864c2d5 Subject: Le poste (seat) @SEAT_ID@ a été retiré Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Le poste (seat) @SEAT_ID@ a été retiré et n'est plus disponible. -- c7a787079b354eaaa9e77b371893cd27 Subject: Changement d'heure Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'horloge système a été modifiée et positionnée à @REALTIME@ microsecondes après le 1er janvier 1970. -- 45f82f4aef7a4bbf942ce861d1f20990 Subject: Fuseau horaire modifié en @TIMEZONE@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Le fuseau horaire du système a été modifié et positionné à @TIMEZONE@. -- b07a249cd024414a82dd00cd181378ff Subject: Le démarrage du système est terminé Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Tous les services nécessaires au démarrage du système ont été lancés. Notez que cela ne signifie pas que le système est maintenant au repos, car des services peuvent encore être en train de terminer leur démarrage. Le chargement du noyau a nécessité @KERNEL_USEC@ microsecondes. Le chargement du « RAM disk » initial a nécessité @INITRD_USEC@ microsecondes. Le chargement de l'espace utilisateur a nécessité @USERSPACE_USEC@ microsecondes. -- eed00a68ffd84e31882105fd973abdd1 Subject: Le démarrage du gestionnaire utilisateur est terminé Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'instance du gestionnaire d'utilisateurs pour l'utilisateur @_UID@ a été démarrée. Tous les services en file d'attente pour démarrer ont été lancés. Notez que des services peuvent être encore en train de démarrer, ou d'autres être lancés à tout moment ultérieur. Le démarrage du gestionnaire a nécéssité @USERSPACE_USEC@ microsecondes. -- 6bbd95ee977941e497c48be27c254128 Subject: Le système entre dans l'état de repos (sleep state) @SLEEP@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Le système est maintenant à l'état de repos (sleep state) @SLEEP@. -- 8811e6df2a8e40f58a94cea26f8ebf14 Subject: Le système sorti de l'état de repos (sleep state) @SLEEP@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Le système est maintenant sorti de l'état de repos (sleep state) @SLEEP@. -- 98268866d1d54a499c4e98921d93bc40 Subject: Arrêt du système amorcé Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'arrêt du système a été amorcé. L'arrêt a maintenant commencé, tous les services du système sont terminés et tous les systèmes de fichiers sont démontés. -- 7d4958e842da4a758f6c1cdc7b36dcc5 Subject: L'unité (unit) @UNIT@ a commencé à démarrer Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'unité (unit) @UNIT@ a commencé à démarrer. -- 39f53479d3a045ac8e11786248231fbf Subject: L'unité (unit) @UNIT@ a terminé son démarrage Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'unité (unit) @UNIT@ a terminé son démarrage, avec le résultat @JOB_RESULT@. -- de5b426a63be47a7b6ac3eaac82e2f6f Subject: L'unité (unit) @UNIT@ a commencé à s'arrêter Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'unité (unit) @UNIT@ a commencé à s'arrêter. -- 9d1aaa27d60140bd96365438aad20286 Subject: L'unité (unit) @UNIT@ a terminé son arrêt Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'unité (unit) @UNIT@ a terminé son arrêt. -- be02cf6855d2428ba40df7e9d022f03d Subject: L'unité (unit) @UNIT@ a échoué Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'unité (unit) @UNIT@ a échoué, avec le résultat @JOB_RESULT@. -- d34d037fff1847e6ae669a370e694725 Subject: L'unité (unit) @UNIT@ a commencé à recharger sa configuration Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'unité (unit) @UNIT@ a commencé à recharger sa configuration. -- 7b05ebc668384222baa8881179cfda54 Subject: L'unité (unit) @UNIT@ a terminé de recharger configuration Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'unité (unit) @UNIT@ a terminé de recharger configuration, avec le résultat @JOB_RESULT@. -- 641257651c1b4ec9a8624d7a40a9e1e7 Subject: Le processus @EXECUTABLE@ n'a pas pu être exécuté Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Le processus @EXECUTABLE@ n'a pas pu être exécuté, et a donc échoué. Le code d'erreur renvoyé est @ERRNO@. -- 0027229ca0644181a76c4e92458afa2e Subject: Un ou plusieurs messages n'ont pas pu être transmis à syslog Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Un ou plusieurs messages n'ont pas pu être transmis au service syslog s'exécutant conjointement avec journald. Cela indique généralement que l'implémentation de syslog utilisée n'a pas été capable de suivre la cadence du flux de messages. -- 1dee0369c7fc4736b7099b38ecb46ee7 Subject: Le point de montage n'est pas vide Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Le répertoire @WHERE@ est spécifié comme point de montage (second champ du fichier /etc/fstab, ou champ Where= dans une unité (unit) systemd) et n'est pas vide. Cela ne perturbe pas le montage du système de fichiers, mais les fichiers préalablement présents dans ce répertoire sont devenus inaccessibles. Pour atteindre ces fichiers, veuillez monter manuellement le système de fichiers sous-jacent à un autre emplacement. -- 24d8d4452573402496068381a6312df2 Subject: Une machine virtuelle ou un conteneur (container) a été démarré Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support La machine virtuelle @NAME@ a été démarrée avec le PID maître @LEADER@, et est maintenant prête à l'emploi. -- 58432bd3bace477cb514b56381b8a758 Subject: Une machine virtuelle ou un conteneur (container) a été arrêté Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support La machine virtuelle @NAME@ avec le PID maître @LEADER@ a été arrêtée. -- 36db2dfa5a9045e1bd4af5f93e1cf057 Subject: Le mode DNSSEC a été désactivé, car il n'est pas supporté par le serveur Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) resolved.conf(5) Le service de résolution (systemd-resolved.service) a détecté que le serveur DNS configuré ne supporte pas DNSSEC, et la validation DNSSEC a donc été désactivée. Cet évènement se produit si DNSSEC=allow-downgrade est configuré dans resolved.conf et que le serveur DNS configuré n'est pas compatible avec DNSSEC. Veuillez noter que ce mode permet des attaques de rétrogradation DNSSEC, car un attaquant peut être capable de désactiver la validation DNSSEC sur le système en injectant des réponses DNS dans le canal de communication. Cet évènement indique que le serveur DNS est effectivement incompatible avec DNSSEC, ou qu'un attaquant a peut-être conduit une telle attaque avec succès. -- 1675d7f172174098b1108bf8c7dc8f5d Subject: La validation DNSSEC a échoué Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) Une requête ou une ressource DNS n'a pas passé la validation DNSSEC. Ceci est généralement une indication que le canal de communication a été altéré. -- 4d4408cfd0d144859184d1e65d7c8a65 Subject: Une ancre de confiance DNSSEC a été révoquée Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) Une ancre de confiance DNSSEC a été révoquée. Une nouvelle ancre de confiance doit être configurée, ou le système d'exploitation a besoin d'être mis à jour, pour fournir une version à jour de l'ancre de confiance. -- 5eb03494b6584870a536b337290809b3 Subject: Le redémarrage automatique d'une unité (unit) a été planifié Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Le redémarrage automatique de l'unité (unit) @UNIT@ a été planifié, en raison de sa configuration avec le paramètre Restart=. -- ae8f7b866b0347b9af31fe1c80b127c0 Subject: Ressources consommées durant l'éxécution de l'unité (unit) Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'unité (unit) @UNIT@ s'est arrêtée et a consommé les ressources indiquées. -- 50876a9db00f4c40bde1a2ad381c3a1b Subject: Le système est configuré d'une manière qui pourrait causer des problèmes Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Les étiquettes suivantes sont possibles : - "split-usr" — /usr est un système de fichiers séparé et nétait pas monté quand systemd a été démarré - "cgroups-missing" — le noyau a été compilé sans le support des groupes de contrôle (cgroups) ou l'accès aux fichiers d'interface est restreint - "var-run-bad" — /var/run n'est pas un lien symbolique vers /run - "overflowuid-not-65534" — l'ID utilisé par le noyau pour l'utilisateur "unknown" (avec NFS ou l'espace de noms utilisateurs) n'est pas 65534 - "overflowgid-not-65534" — l'ID utilisé par le noyau pour le groupe "unknown" (avec NFS ou l'espace de noms utilisateurs) n'est pas 65534 Le présent système est étiqueté @TAINT@. PK �v�Z:�+:X? X? systemd.it.catalognu �[��� # SPDX-License-Identifier: LGPL-2.1-or-later # # Copyright © 2013-2019 Daniele Medri # Message catalog for systemd's own messages # Italian translation # Il formato dei messaggi di catalogo è descritto (in inglese) qui: # https://www.freedesktop.org/wiki/Software/systemd/catalog # Subject: The Journal has been started -- f77379a8490b408bbe5f6940505a777b Subject: Il registro è stato avviato Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Il processo relativo al registro di sistema è stato avviato, ha aperto i file in scrittura ed è ora pronto a gestire richieste. # Subject: The Journal has been stopped -- d93fb3c9c24d451a97cea615ce59c00b Subject: Il registro è stato terminato Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Il processo relativo al registro di sistema è stato terminato e ha chiuso tutti i file attivi. # Subject: Disk space used by the journal -- ec387f577b844b8fa948f33cad9a75e6 Subject: Spazio disco utilizzato dal journal Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support @JOURNAL_NAME@ (@JOURNAL_PATH@) sta attualmente utilizzando @CURRENT_USE_PRETTY@. L'utilizzo massimo consentito è impostato a @MAX_USE_PRETTY@. Si lasciano liberi almeno @DISK_KEEP_FREE_PRETTY@ (attuale spazio libero: @DISK_AVAILABLE_PRETTY@). Il limite di utilizzo forzato è quindi @LIMIT_PRETTY@, con @AVAILABLE_PRETTY@ ancora disponibili. I limiti di controllo dello spazio disco utilizzati dal Journal possono essere configurati con le impostazioni SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= nel file di configurazione /etc/systemd/journald.conf. Guardare journald.conf(5) per i dettagli. # Subject: Messages from a service have been suppressed -- a596d6fe7bfa4994828e72309e95d61e Subject: I messaggi di un servizio sono stati soppressi Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:journald.conf(5) Un servizio ha registrato troppi messaggi in un dato periodo di tempo. I messaggi del servizio sono stati eliminati. Solo i messaggi del servizio indicato sono stati eliminati, i messaggi degli altri servizi rimangono invariati. I limiti oltre i quali si eliminano i messaggi si configurano con RateLimitIntervalSec= e RateLimitBurst= in /etc/systemd/journald.conf. Vedi journald.conf(5) per maggiori informazioni. # Subject: Journal messages have been missed -- e9bf28e6e834481bb6f48f548ad13606 Subject: I messaggi di un servizio sono stati perduti Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support I messaggi del kernel sono andati persi perché il registro di sistema non è stato in grado di gestirli abbastanza velocemente. # Subject: Process @COREDUMP_PID@ (@COREDUMP_COMM@) dumped core -- fc2e22bc6ee647b6b90729ab34a250b1 Subject: Il processo @COREDUMP_PID@ (@COREDUMP_COMM@) ha generato un dump. Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:core(5) Il processo @COREDUMP_PID@ (@COREDUMP_COMM@) si è bloccato generando un dump. Questo di solito capita per un errore di programmazione nell'applicazione e dovrebbe essere segnalato come bug al vendor. # Subject: Core file was truncated to @SIZE_LIMIT@ bytes -- 5aadd8e954dc4b1a8c954d63fd9e1137 Subject: Il Core file è stato troncato a @SIZE_LIMIT@ bytes. Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:coredump.conf(5) Il processo ha più memoria mappata del limite massimo configurato da systemd-coredump(8) per processare e memorizzare. Solo i primi @SIZE_LIMIT@ bytes sono stati salvati. Il file potrebbe essere ancora utile, ma strumenti come gdb(1) dovrebbero segnalare la troncatura. # Subject: A new session @SESSION_ID@ has been created for user @USER_ID@ -- 8d45620c1a4348dbb17410da57c60c66 Subject: La nuova sessione @SESSION_ID@ è stata creata per l'utente @USER_ID@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Una nuova sessione con ID @SESSION_ID@ è stata creata per l'utente @USER_ID@. Il processo primario della sessione è @LEADER@. # Subject: A new seat @SEAT_ID@ has been terminated -- 3354939424b4456d9802ca8333ed424a Subject: La sessione @SESSION_ID@ è terminata Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) La sessione con ID @SESSION_ID@ è terminata. # Subject: A new seat @SEAT_ID@ is now available -- fcbefc5da23d428093f97c82a9290f7b Subject: La nuova postazione @SEAT_ID@ è ora disponibile Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) La nuova postazione @SEAT_ID@ è stata configurata ed è ora disponibile. # Subject: A seat @SEAT_ID@ has been removed -- e7852bfe46784ed0accde04bc864c2d5 Subject: La postazione @SEAT_ID@ è stata rimossa Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) La postazione @SEAT_ID@ è stata rimossa e non è più disponibile. # Subject: Time Change -- c7a787079b354eaaa9e77b371893cd27 Subject: Cambio d'orario Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'orologio di sistema è cambiato in @REALTIME@ microsecondi dal 1 gennaio, 1970. # Subject: Time zone change to @TIMEZONE@ -- 45f82f4aef7a4bbf942ce861d1f20990 Subject: Il fuso orario è cambiato in @TIMEZONE@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Il fuso orario di sistema è cambiato in @TIMEZONE@. # Subject: System start-up is now complete -- b07a249cd024414a82dd00cd181378ff Subject: Avvio del sistema completato. Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Tutti i servizi di sistema richiesti per la fase di avvio sono stati eseguiti con successo. La macchina potrebbe ancora attendere i servizi attivati sono in fase di completamento. L'avvio del kernel ha richiesto @KERNEL_USEC@ microsecondi. L'avvio del disco RAM ha richiesto @INITRD_USEC@ microsecondi. L'avvio dello userspace ha richiesto @USERSPACE_USEC@ microsecondi. # Subject: User manager start-up is now complete -- eed00a68ffd84e31882105fd973abdd1 Subject: L'istanza di gestione per l'utente è completata Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'istanza di gestione per l'utente @_UID@ è stata avviata. Tutti i servizi interrogati sono stati avviati. Altri servizi potrebbero essere ancora in fase di avvio o in attesa di essere avviati. L'avvio dell'istanza ha impiegato @USERSPACE_USEC@ microsecondi. # Subject: System sleep state @SLEEP@ entered -- 6bbd95ee977941e497c48be27c254128 Subject: Il sistema è entrato in fase di pausa @SLEEP@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Il sistema è entrato nello stato di pausa @SLEEP@. # Subject: System sleep state @SLEEP@ left -- 8811e6df2a8e40f58a94cea26f8ebf14 Subject: Il sistema è uscito dalla fase di pausa @SLEEP@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Il sistema è uscito dallo stato di pausa @SLEEP@. # Subject: System shutdown initiated -- 98268866d1d54a499c4e98921d93bc40 Subject: Il sistema è in fase di spegnimento Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Systemd è in fase di spegnimento. Tutti i servizi di sistema saranno terminati e tutti i file systems smontati. # Subject: Unit @UNIT@ has begun with start-up -- 7d4958e842da4a758f6c1cdc7b36dcc5 Subject: L'unità @UNIT@ inizia la fase di avvio Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'unità @UNIT@ ha iniziato la fase di avvio. # Subject: Unit @UNIT@ has finished start-up -- 39f53479d3a045ac8e11786248231fbf Subject: L'unità @UNIT@ ha terminato la fase di avvio Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'unità @UNIT@ ha terminato la fase di avvio. La fase di avvio è @JOB_RESULT@. # Subject: Unit @UNIT@ has begun shutting down -- de5b426a63be47a7b6ac3eaac82e2f6f Subject: L'unità @UNIT@ ha iniziato la fase di spegnimento Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'unità @UNIT@ ha iniziato la fase di spegnimento. # Subject Unit @UNIT@ has finished shutting down -- 9d1aaa27d60140bd96365438aad20286 Subject: L'unità @UNIT@ ha terminato la fase di spegnimento Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'unità @UNIT@ ha terminato la fase di spegnimento. # Subject: Unit @UNIT@ has failed -- be02cf6855d2428ba40df7e9d022f03d Subject: L'unità @UNIT@ è fallita Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'unità @UNIT@ è fallita. Il risultato è @JOB_RESULT@. # Subject: Unit @UNIT@ has begun with reloading its configuration -- d34d037fff1847e6ae669a370e694725 Subject: L'unità @UNIT@ è iniziata con il ricaricamento della propria configurazione Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'unità @UNIT@ è iniziata con il ricaricamento della propria configurazione # Subject: Unit @UNIT@ has finished reloading its configuration -- 7b05ebc668384222baa8881179cfda54 Subject: L'unità @UNIT@ è terminata con il ricaricamento della propria configurazione Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support L'unità @UNIT@ è terminata con il ricaricamento della propria configurazione Il risultato è @JOB_RESULT@. # Subject: Process @EXECUTABLE@ could not be executed -- 641257651c1b4ec9a8624d7a40a9e1e7 Subject: Il processo @EXECUTABLE@ non può essere eseguito Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Il processo @EXECUTABLE@ non può essere eseguito e termina. Il numero di errore restituito durante l'esecuzione del processo è @ERRNO@. # Subject: One or more messages could not be forwarded to syslog -- 0027229ca0644181a76c4e92458afa2e Subject: Uno o più messaggi non possono essere inoltrati a syslog Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Uno o più messaggi non possono essere inviati al servizio syslog eseguito in parallelo a journald. Questo di solito capita perché, l'implementazione di syslog non sta al passo con la velocità dei messaggi accodati. # Subject: Mount point is not empty -- 1dee0369c7fc4736b7099b38ecb46ee7 Subject: Il punto di montaggio non è vuoto Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support La directory @WHERE@ è specificata come punto di montaggio (secondo campo in /etc/fstab o nel campo Where= del file unità di systemd) e non è vuoto. Questo non interferisce con il montaggio, ma i file pre-esistenti in questa directory diventano inaccessibili. Per visualizzare i file, si suggerisce di montare manualmente il file system indicato in una posizione secondaria. # Subject: A virtual machine or container has been started -- 24d8d4452573402496068381a6312df2 Subject: Avviata macchina virtuale o container Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support La macchina virtuale @NAME@ con PID primario @LEADER@ è stata avviata ed è pronta all'uso. # Subject: A virtual machine or container has been terminated -- 58432bd3bace477cb514b56381b8a758 Subject: Terminata macchina virtuale o container Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support La macchina virtuale @NAME@ con PID primario @LEADER@ è stata terminata. # Subject: DNSSEC mode has been turned off, as server doesn't support it -- 36db2dfa5a9045e1bd4af5f93e1cf057 Subject: La modalità DNSSEC è stata spenta, il server non la supporta Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) resolved.conf(5) Il servizio di risoluzione (systemd-resolved.service) ha rilevato che il server DNS indicato non supporta DNSSEC e la validazione di quest'ultimo tipo è stata conseguentemente disabilitata. Ciò avverrà se DNSSEC=allow-downgrade è configurato nel file resolved.conf e il server DNS indicato è incompatibile con DNSSEC. In questo modo ci si espone ad attacchi "DNSSEC downgrade", e un aggressore potrebbe disabilitare la validazione DNSSEC sul sistema inserendo risposte DNS nel canale di comunicazione. Questo evento potrebbe indicare un'incompatibilità del DNS Server con DNSSEC o che un aggressore è riuscito nel suo intento malevolo. # Subject: DNSSEC validation failed -- 1675d7f172174098b1108bf8c7dc8f5d Subject: La validazione DNSSEC è fallita Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) Una query DNS o un dato hanno fatto fallire la validazione DNSSEC. Questo è usualmente un segnale che il canale di comunicazione utilizzato è stato manomesso. # Subject: A DNSSEC trust anchor has been revoked -- 4d4408cfd0d144859184d1e65d7c8a65 Subject: Un trust anchor DNSSEC è stato revocato Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) Un trust anchor DNSSEC è stato revocato. Un nuovo punto di fiducia è stato riconfigurato o il sistema operativo deve essere aggiornato per fornire un nuovo ancoraggio. # Subject: Automatic restarting of a unit has been scheduled -- 5eb03494b6584870a536b337290809b3 Subject: Il riavvio automatico di un'unità è stato schedulato Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Il riavvio automatico dell'unità @UNIT@ è stato schedulato, come risultato delle impostazioni configurate in Restart=. # Subject: Resources consumed by unit runtime -- ae8f7b866b0347b9af31fe1c80b127c0 Subject: Risorse utilizzate dall'unità in esecuzione Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Unità @UNIT@ terminata consumando le indicate risorse. # Subject: Unit succeeded -- 7ad2d189f7e94e70a38c781354912448 Subject: Unità terminata Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Unità @UNIT@ entrata con successo nello stato 'dead' (morto). # Subject: Unit failed -- d9b373ed55a64feb8242e02dbe79a49c Subject: Unit fallita Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Unità @UNIT@ entrata nello stato 'failed' (fallito) con risultato '@UNIT_RESULT@'. # Subject: Unit process exited -- 98e322203f7a4ed290d09fe03c09fe15 Subject: Uscito processo unità Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Un processo @COMMAND@ appartenente all'unità @UNIT@ è uscito. Il codice di uscita del processo è '@EXIT_CODE@' ed è uscito con @EXIT_STATUS@. # Subject: The system is configured in a way that might cause problems -- 50876a9db00f4c40bde1a2ad381c3a1b Subject: Il sistema è configurato in un modo che potrebbe causare problemi Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support I seguenti "tags" sono possibili: - "split-usr" — /usr è un file system separato e non è stato montato all'avvio di systemd - "cgroups-missing" — il kernel era compilato senza supporto cgroup o l'accesso ai file attesi è ristretto. - "var-run-bad" — /var/run non è un link simbolico (symlink) a /run - "overflowuid-not-65534" — l'ID usato dal kernel per gli utenti "unknown" (tipo NFS o user namespace) non è 65534 - "overflowgid-not-65534" — l'ID usato dal kernel per il gruppo "unknown" (tipo NFS o user namespace) non è 65534 L'attuale sistema è taggato come @TAINT@. # Subject: A process of @UNIT@ unit has been killed by the OOM killer. -- fe6faa94e7774663a0da52717891d8ef Subject: Un processo dell'unità @UNIT@ è stato terminato da un OOM killer. Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Un processo dell'unità @UNIT@ è stato terminato dalla logica del kernel Linux per gestire gli eventi out-of-memory (OOM). In altri termini, il sistema ha poca memoria e dovrebbe essere liberata. Un processo associato con @UNIT@ è stato identificato come il processo ideale da terminare e così è stato. La pressione sulla memoira potrebbe o meno essere causata da @UNIT@. PK �v�Zr���Ps Ps systemd.bg.catalognu �[��� # SPDX-License-Identifier: LGPL-2.1-or-later # # Copyright © 2016, 2022 Alexander Shopov <ash@kambanaria.org> # Message catalog for systemd's own messages # The catalog format is documented on # https://www.freedesktop.org/wiki/Software/systemd/catalog # For an explanation why we do all this, see https://xkcd.com/1024/ -- f77379a8490b408bbe5f6940505a777b Subject: Журналният процес е пуснат Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Журналният процес на системата е стартирал, отворил е журналните файлове за запис и може да приема заявки. -- d93fb3c9c24d451a97cea615ce59c00b Subject: Журналният процес е спрян Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Журналният процес на системата е спрян, затворени са всички отворени журнални файлове. -- ec387f577b844b8fa948f33cad9a75e6 Subject: Пространство върху диска заето от журналните файлове Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support @JOURNAL_NAME@ (@JOURNAL_PATH@) в момента заема @CURRENT_USE_PRETTY@. Максималният зададен размер е @MAX_USE_PRETTY@. Свободни се оставят поне @DISK_KEEP_FREE_PRETTY@ (от текущо наличните @DISK_AVAILABLE_PRETTY@). Максималният наложен размер е @LIMIT_PRETTY@, от който @AVAILABLE_PRETTY@ са свободни. Настройките за максималния размер на журнала върху диска се управляват чрез директивите „SystemMaxUse=“, „SystemKeepFree=“, „SystemMaxFileSize=“, „RuntimeMaxUse=“, „RuntimeKeepFree=“ и „RuntimeMaxFileSize=“ във файла „/etc/systemd/journald.conf“. За повече информация прегледайте „journald.conf(5)“ от ръководството. -- a596d6fe7bfa4994828e72309e95d61e Subject: Съобщенията от някоя услуга са отхвърлени Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:journald.conf(5) Някоя услуга генерира прекалено много съобщения за кратък период. Част от нейните съобщения са отхвърляни. Съобщенията от другите услуги не са засегнати. Настройките за максималния брой съобщения, които ще се обработят, се управляват чрез директивите „RateLimitInterval=“ и „RateLimitBurst=“ във файла „/etc/systemd/journald.conf“. За повече информация прегледайте „journald.conf(5)“ от ръководството. -- e9bf28e6e834481bb6f48f548ad13606 Subject: Пропуснати журнални съобщения Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Някои от съобщенията на ядрото може и да са пропуснати, защото системата не смогваше да ги обработи достатъчно бързо. -- fc2e22bc6ee647b6b90729ab34a250b1 Subject: Процес @COREDUMP_PID@ (@COREDUMP_COMM@) запази освободената памет Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:core(5) Процес @COREDUMP_PID@ (@COREDUMP_COMM@) заби, представянето му в паметта бе запазено. Най-често това се дължи на грешка в забилата програма и следва да я докладвате на създателите на програмата. -- 5aadd8e954dc4b1a8c954d63fd9e1137 Subject: Файлът с представяне в паметта е отрязан до @SIZE_LIMIT@ байта Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:coredump.conf(5) Заделената памет за процеса надвишава настроения максимум за обработка и съхранение от systemd-coredump(8). Запазени са само първите @SIZE_LIMIT@ байта. Този файл (core) може да се окаже полезен, въпреки че е отсечен. Част от инструментите за работа като gdb(1) може да изведат предупреждение за отсичането. -- 8d45620c1a4348dbb17410da57c60c66 Subject: Създадена е нова сесия @SESSION_ID@ за потребителя @USER_ID@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) За потребителя „@USER_ID@“ е създадена нова сесия @SESSION_ID@. Водещият процес на сесията е @LEADER@ -- 3354939424b4456d9802ca8333ed424a Subject: Сесия @SESSION_ID@ приключи Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Сесия @SESSION_ID@ приключи работа. -- fcbefc5da23d428093f97c82a9290f7b Subject: Налично е ново работно място @SEAT_ID@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Новото работно място @SEAT_ID@ е настроено и готово за работа. -- e7852bfe46784ed0accde04bc864c2d5 Subject: Работното място @SEAT_ID@ е премахнато Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Работното място @SEAT_ID@ вече не е налично. -- c7a787079b354eaaa9e77b371893cd27 Subject: Смяна на системното време Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Часовникът на системата е сверен да сочи @REALTIME@ микросекунди след 1 януари 1970. -- 45f82f4aef7a4bbf942ce861d1f20990 Subject: Смяна на часовия пояс да е @TIMEZONE@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Часовият пояс на системата е сменен на „@TIMEZONE@“. -- b07a249cd024414a82dd00cd181378ff Subject: Стартирането на системата завърши Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Успешно са стартирали всички услуги, които са посочени за задействане при стартиране на системата. Това не означава, че системата бездейства, защото някои от услугите може да извършват специфични действия при стартиране. Стартирането на ядрото отне @KERNEL_USEC@ микросекунди. Стартирането на RAM диска за първоначално зареждане отне @INITRD_USEC@ микросекунди. Стартирането на потребителските програми отне @USERSPACE_USEC@ микросекунди. -- eed00a68ffd84e31882105fd973abdd1 Subject: Стартирането на управлението на потребител завърши Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Процесът за управлението на потребител @_UID@ завърши. Всички услуги насрочени за това са стартиране, но може да има други услуги, които да предстои да се стартират. Стартирането на управлението на потребител отне @USERSPACE_USEC@ микросекунди. -- 6bbd95ee977941e497c48be27c254128 Subject: Системата е приспана на ниво @SLEEP@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Системата премина в състояние на приспиване „@SLEEP@“. -- 8811e6df2a8e40f58a94cea26f8ebf14 Subject: Системата се събуди след приспиване на ниво @SLEEP@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Системата се събуди от състояние на приспиване „@SLEEP@“. -- 98268866d1d54a499c4e98921d93bc40 Subject: Започна процедура на спиране на системата Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Започна процедурата на Systemd за спиране на системата. Всички процеси и услуги се спират, всички файлови системи се демонтират. -- c14aaf76ec284a5fa1f105f88dfb061c Subject: Започна процедура за връщане на заводските настройки на системата Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Започна процедура за връщане на заводските настройки на системата. Самото действие е изцяло определено от имплементацията. Типично се връщат заводското състояние и настройки от производителя. -- 7d4958e842da4a758f6c1cdc7b36dcc5 Subject: Модул @UNIT@ се стартира Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Модулът „@UNIT@“ се стартира в момента. Идентификаторът на задача е @JOB_ID@. -- 39f53479d3a045ac8e11786248231fbf Subject: Модул @UNIT@ вече е стартиран Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Стартирането на модул „@UNIT@“ завърши. Идентификаторът на задача е @JOB_ID@. -- be02cf6855d2428ba40df7e9d022f03d Subject: Модул @UNIT@ не успя да стартира Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Модулът „@UNIT@“ не успя да стартира. Идентификаторът на задача е @JOB_ID@, а резултатът от нея е @JOB_RESULT@. -- de5b426a63be47a7b6ac3eaac82e2f6f Subject: Модул @UNIT@ се спира Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Модулът „@UNIT@“ се спира в момента. Идентификаторът на задача е @JOB_ID@. -- 9d1aaa27d60140bd96365438aad20286 Subject: Модул @UNIT@ вече е спрян Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Спирането на модул „@UNIT@“ завърши. Идентификаторът на задача е @JOB_ID@, а резултатът от нея е @JOB_RESULT@. -- d34d037fff1847e6ae669a370e694725 Subject: Модул @UNIT@ започна презареждане на настройките си Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Модулът „@UNIT@“ започна презареждане на настройките си.( Идентификаторът на задача е @JOB_ID@.) -- 7b05ebc668384222baa8881179cfda54 Subject: Модулът @UNIT@ завърши презареждането на настройките си Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Модулът „@UNIT@“ завърши презареждането на настройките си. Резултатът e: @JOB_RESULT@ -- 641257651c1b4ec9a8624d7a40a9e1e7 Subject: Програмата @EXECUTABLE@ не успя да се стартира Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Програмата „@EXECUTABLE@“ не успя да се стартира. Върнатият номер на грешка е: @ERRNO@. -- 0027229ca0644181a76c4e92458afa2e Subject: Поне едно съобщение не бе препратено към syslog Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Поне едно съобщение не бе препратено към журналната услуга syslog, която работи успоредно с journald. Най-често това указва, че тази реализация на syslog не може да поеме текущия обем съобщения. -- 1dee0369c7fc4736b7099b38ecb46ee7 Subject: Точката за монтиране не е празна Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Директорията „@WHERE@“ не е празна. Тя е указана като точка за монтиране — или като второ поле във файла „/etc/fstab“, или чрез директивата „Where=“ в някой от файловете за модул на Systemd. Това не пречи на самото монтиране, но вече съществуващите там файлове и директории няма да се виждат повече, освен ако ръчно не монтирате тази непразна директория някъде другаде. -- 24d8d4452573402496068381a6312df2 Subject: Стартирана е виртуална машина или контейнер Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Виртуалната машина „@NAME@“ с идентификатор на водещия процес @LEADER@ е стартирана и готова за работа. -- 58432bd3bace477cb514b56381b8a758 Subject: Спряна е виртуална машина или контейнер Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Виртуалната машина „@NAME@“ с идентификатор на водещия процес @LEADER@ е спряна. -- 36db2dfa5a9045e1bd4af5f93e1cf057 Subject: Режимът DNSSEC е изключен, защото сървърът не го поддържа Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) Documentation: man:resolved.conf(5) Локалната услуга за имена (systemd-resolved.service) установи, че настроеният сървър за DNS не поддържа DNSSEC, затова този режим е изключен. Това се случва, когато директивата „DNSSEC=allow-downgrade“ е включена във файла „resolved.conf“ и зададеният сървър за DNS не е съвместим с DNSSEC. Внимавайте, защото това може да позволи атака, при която трета страна ви връща отговори, които да предизвикат понижаването на сигурността от DNSSEC до DNS. Такова събитие означава, че или сървърът за DNS не е съвместим с DNSSEC, или някой успешно ви е атакувал за понижаване на сигурността на имената. -- 1675d7f172174098b1108bf8c7dc8f5d Subject: Неуспешна проверка на DNSSEC Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) Заявка или запис в DNS не издържа̀ проверка с DNSSEC. Това обикновено показва вмешателство на трета страна в канала ви за връзка. -- 4d4408cfd0d144859184d1e65d7c8a65 Subject: Анулирана доверена котва в DNSSEC Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) Анулирана е доверена котва за DNSSEC и трябва да настроите нова. Понякога новата идва с обновяване на системата. -- 5eb03494b6584870a536b337290809b3 Subject: Насрочено е автоматично рестартиране на модул Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Насрочено е автоматично рестартиране на модула „@UNIT@“ в следствие на директивата „Restart=“. -- ae8f7b866b0347b9af31fe1c80b127c0 Subject: Модулът консумира ресурсите Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Модулът „@UNIT@“ завърши работа и изконсумира указаните ресурси. -- 7ad2d189f7e94e70a38c781354912448 Subject: Успешен модул Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Модулът „@UNIT@“ успешно премина в „мъртво“ състояние (dead). -- 0e4284a0caca4bfc81c0bb6786972673 Subject: Прескочен модул Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Модулът „@UNIT@“ е прескочен поради неуспешно изпълнение на командата в директивата „ExecCondition=“ и премина в „мъртво“ състояние (dead) с резултат „@UNIT_RESULT@“. -- d9b373ed55a64feb8242e02dbe79a49c Subject: Неуспешен модул Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Модулът „@UNIT@“ премина в състояние за неуспех „failed“ с резултат „@UNIT_RESULT@“. -- 98e322203f7a4ed290d09fe03c09fe15 Subject: Завършил модул Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Процесът, настроен за „@COMMAND@=“ към модула „@UNIT@“ завърши работа. Изходният код е „@EXIT_CODE@“, а изходното състояние — „@EXIT_STATUS@“. -- 50876a9db00f4c40bde1a2ad381c3a1b Subject: Настройките на системата може да доведат до проблеми Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Възможни са следните етикети: ⁃ „split-usr“ — „/usr“ е отделна файлова система, която не е била монтирана при стартирането на systemd ⁃ „cgroups-missing“ — ядрото е компилирано без поддръжка на „cgroup“ или е ограничен достъпът до тази подсистема ⁃ „var-run-bad“ — „/var/run“ не е символна връзка към „/run“ ⁃ "overflowuid-not-65534“ — идентификаторът на непознатия потребител („unknown“) за NFS или пространство за имена на потребители не е е 65534 ⁃ „overflowgid-not-65534“ — идентификаторът на непознатата група („unknown“) за NFS или пространство за имена на групи не е е 65534 Текущо системата е отбелязана като „@TAINT@“. -- fe6faa94e7774663a0da52717891d8ef Subject: Процес от модула „@UNIT@“ е убит поради липса на памет Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Процес от модула „@UNIT@“ е убит от подсистемата на Linux за работа при недостиг на памет (OOM killer). Това обикновено означава, че системата е имала малко памет и се е наложило аварийното ѝ освобождаване. Някой процес от модула „@UNIT@“ е бил набелязан като най-добрия кандидат и е бил убит от ядрото. Note that the memory pressure might or might not have been caused by @UNIT@. -- b61fdac612e94b9182285b998843061f Subject: Позволено име на потребител/група @USER_GROUP_NAME@ не съответства на строгите правила за именоване Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: https://systemd.io/USER_NAMES Указано е име на потребител/група „@USER_GROUP_NAME@“. То е прието, защото отговаря на облекчените. Въпреки това то не отговаря на строгите правила. Те съответстват на регулярния израз: ^[a-zA-Z_][a-zA-Z0-9_-]{0,30}$ Облекчените правила приемат всички имена без празния низ; имената съдържащи нулев байт, контролни знаци, „:“ или „/“; имена, които не са в UTF-8; имена които почват или завършват с празни знаци; които са „.“ или „..“; които съдържат само цифри; които започват с „-“ и продължават само с цифри. -- 1b3bb94037f04bbf81028e135a12d293 Subject: Не може да се избере име за модул на базата на пътя @MOUNT_POINT@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Следната точка за монтиране не може да се преобразува в име на монтиращ модул (.mount): @MOUNT_POINT@ Най-често това се дължи на факта, че пътят за монтиране е по-дълъг от максимума за име на модул. systemd динамично задава модули „.mount“ за всички монтирани ресурси в системата. Затова се ползва прост алгоритъм за екраниране на знаци — взема се абсолютния път, всички знаци „/“ се заменят с „-“ (с изключение на водещия, който се пропуска). Всички знаци извън буквите и числата (вкл. „:“, „-“, „_“, „.“, „\“) се заменят с „\xNN“, където NN е шестнадесетичният код на знака. Добавя се и суфиксът „.mount“. Полученият низ трябва да е по-къс от 256 знака, за да се ползва за име на модул. Ограничението цели всички имена на модули да може да са и имена на файлове. Ако низът за име е по-дълъг, той не може да се ползва за име на модул. В такъв случай systemd няма да създаде модул и няма да може да се ползва за управление на точката на монтиране. Тя няма да се появява в таблицата с модули на мениджъра на системата и съответно няма да се извършва безопасно изключване при изключването на системата. Препоръчваме да не ползвате толкова дълги имена като точки за монтиране. Ако все пак ги ползвате, ще трябва да ги управлявате независимо от systemd, т.е. сами администрирайте монтирането и изключването. -- b480325f9c394a7b802c231e51a2752c Subject: Настроен е специален потребител @OFFENDING_USER@ — това е опасно! Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: https://systemd.io/UIDS-GIDS Модулът „@UNIT@“ е настроен да ползва директивата „User=@OFFENDING_USER@“. Това е опасно. Основното предназначение на „@OFFENDING_USER@“ на системите на база Linux е да е собственик на файловете със собственик, който не е известен на локалната система. Този потребител се ползва най-вече от клиента за NFS и пространствата за имена за потребители. Ако този модул стартира процеси от името на този потребител, те може да получат достъп до файловете, които са с неизвестен собственик. Силно препоръчване да стартирате процеси с този потребител, особено на системи ползващи NFS или контейнери. Вместо това създайте потребител и негов идентификатор специфичен за тази услуга или статично с „systemd-sysusers“, или динамично чрез директивата на модула „DynamicUser=“. -- 1c0454c1bd2241e0ac6fefb4bc631433 Subject: Модулът systemd-udev-settle.service е остарял Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Препоръчва се да не ползвате остарелия модул на systemd — „systemd-udev-settle.service“. Той нарочно забавя процеса на стартиране, но всъщност не предоставя гаранциите, които другите системи очакват от него. Като цяло е грешка да го ползвате или разчитате на него поради проблеми с паралелността. Традиционно задачата на този модул е да изчака проверката и инициализацията на всички устройства на системата, като завършването на стартирането се отлага до приключването на тази фаза. Днешните системи не работят така — хардуерните устройства се появяват в произволен момент, а проверката и инициализацията им може да отнеме много време. В общия случай стартирането не може да се забави до инициализацията на всички устройства, защото не е добре дефинирано кои са всички устройства и кога се открити. Това се отнася с особено значение за устройствата през USB или тези, които се ползват през мрежата. Програмите, които изискват определен хардуер (напр. мрежово или блоково устройство), трябва изрично да чакат конкретния хардуер да стартира, а останалата работа трябва да е асинхронна, така че инициализацията на всяко устройство да позволява на модулите, зависещи от него, да продължат работа, без да се забавя процеса на стартиране. Ако въпросният софтуер не работи така, а изрично изчаква „systemd-udev-settle.service“, това е грешка и трябва да се поправи. Изпратете доклад на грешка до авторите на следните модули, като поискате да не зависят от „systemd-udev-settle.service“, а само от съответното устройство: @OFFENDING_UNITS@ -- 7c8a41f37b764941a0e1780b1be2f037 Subject: Първоначална синхронизация на часовника Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support За първи път след текущото стартиране е извършена синхронизация със сървър за NTP — системният часовник е настроен. PK �v�Z��h! ! systemd.pt_BR.catalognu �[��� # SPDX-License-Identifier: LGPL-2.1-or-later # # Copyright © 2015 Rafael Ferreira (translation) # Catálogo de mensagens para as mensagens do próprio systemd # O formato do catálogo está documentado em # https://www.freedesktop.org/wiki/Software/systemd/catalog # Para uma explicação do porquê de fazermos tudo isso, veja # https://xkcd.com/1024/ -- f77379a8490b408bbe5f6940505a777b Subject: O jornal foi inciado Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support O processo jornal do sistema foi iniciado, arquivos foram abertos e está pronto para processar requisições. -- d93fb3c9c24d451a97cea615ce59c00b Subject: O jornal foi interrompido Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support O processo do jornal do sistema foi desligado e todos os arquivos de jornal do sistema foram fechados. -- a596d6fe7bfa4994828e72309e95d61e Subject: Mensagens de um serviço foram suprimidas Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:journald.conf(5) Um serviço registrou no log um número excessivo de mensagens dentro de um período de tempo. Mensagens do serviço foram descartadas. Note que apenas mensagens de um serviço em questão foram descartadas; outras mensagens dos serviços não foram afetadas. Os controles de limites de quando as mensagens são descartadas pode ser configurado com RateLimitIntervalSec= e RateLimitBurst= no /etc/systemd/journald.conf. Veja journald.conf(5) para detalhes. -- e9bf28e6e834481bb6f48f548ad13606 Subject: Mensagens do jornal foram perdidas Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Mensagens do kernel foram perdidas pois o sistema do jornal não pôde processá-las em velocidade suficiente para a demanda. -- fc2e22bc6ee647b6b90729ab34a250b1 Subject: Processo @COREDUMP_PID@ (@COREDUMP_COMM@) despejou núcleo Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:core(5) Processo @COREDUMP_PID@ (@COREDUMP_COMM@) travou e despejou o núcleo. Isso normalmente indica um erro de programação no programa que travou e deveria ser relatado para seu fabricante como um erro. -- 8d45620c1a4348dbb17410da57c60c66 Subject: A nova sessão @SESSION_ID@ foi criada para usuário o @USER_ID@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Uma nova sessão com o ID @SESSION_ID@ foi criada para o usuário @USER_ID@. O processo originador da sessão é @LEADER@. -- 3354939424b4456d9802ca8333ed424a Subject: Sessão @SESSION_ID@ foi terminada Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Um sessão com o ID @SESSION_ID@ foi terminada. -- fcbefc5da23d428093f97c82a9290f7b Subject: Um novo seat @SEAT_ID@ está disponível Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Um novo seat @SEAT_ID@ foi configurado e está disponível. -- e7852bfe46784ed0accde04bc864c2d5 Subject: Seat @SEAT_ID@ foi removido agora Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Um seat @SEAT_ID@ foi removido e não está mais disponível. -- c7a787079b354eaaa9e77b371893cd27 Subject: Time change Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support O relógio do sistema foi alterado para @REALTIME@ microssegundos após 1º de janeiro de 1970. -- 45f82f4aef7a4bbf942ce861d1f20990 Subject: Fuso horário alterado para @TIMEZONE@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support O fuso horário do sistema foi alterado para @TIMEZONE@. -- b07a249cd024414a82dd00cd181378ff Subject: Inicialização do sistema foi concluída Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Todos os serviços do sistema necessários que estão enfileirados para executar na inicialização do sistema, foram iniciados com sucesso. Note que isso não significa que a máquina está ociosa, pois os serviços podem ainda estar ocupados com a inicialização completa. Inicialização do kernel precisou @KERNEL_USEC@ microssegundos. Disco de RAM inicial precisou de @INITRD_USEC@ microssegundos. Inicialização do espaço do usuário precisou de @USERSPACE_USEC@ microssegundos. -- 6bbd95ee977941e497c48be27c254128 Subject: Estado de suspensão do sistema @SLEEP@ iniciado Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support O sistema entrou agora no estado de suspensão @SLEEP@. -- 8811e6df2a8e40f58a94cea26f8ebf14 Subject: Estado de suspensão do sistema @SLEEP@ finalizado Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support O sistema saiu agora do estado de suspensão @SLEEP@. -- 98268866d1d54a499c4e98921d93bc40 Subject: Desligamento do sistema iniciado Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Desligamento do sistema foi inicializado. O desligamento se iniciou e todos os serviços do sistema foram terminados e todos os sistemas desmontados. -- 7d4958e842da4a758f6c1cdc7b36dcc5 Subject: Unidade @UNIT@ sendo iniciado Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support A unidade @UNIT@ está sendo iniciada. -- 39f53479d3a045ac8e11786248231fbf Subject: Unidade @UNIT@ concluiu a inicialização Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support A unidade @UNIT@ concluiu a inicialização. The start-up result is @JOB_RESULT@. -- de5b426a63be47a7b6ac3eaac82e2f6f Subject: Unidade @UNIT@ sendo desligado Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support A unidade @UNIT@ está sendo desligada. -- 9d1aaa27d60140bd96365438aad20286 Subject: A unidade @UNIT@ concluiu o desligamento Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support A unidade @UNIT@ concluiu o desligamento. -- be02cf6855d2428ba40df7e9d022f03d Subject: A unidade @UNIT@ falhou Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support A unidade @UNIT@ falhou. O resultado é @JOB_RESULT@. -- d34d037fff1847e6ae669a370e694725 Subject: Unidade @UNIT@ iniciou recarregamento de sua configuração Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support A unidade @UNIT@ iniciou o recarregamento de sua configuração. -- 7b05ebc668384222baa8881179cfda54 Subject: Unidade @UNIT@ concluiu recarregamento de sua configuração Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support A unidade @UNIT@ concluiu o recarregamento de sua configuração. O resultado é @JOB_RESULT@. -- 641257651c1b4ec9a8624d7a40a9e1e7 Subject: Processo @EXECUTABLE@ não pôde ser executado Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support O processo @EXECUTABLE@ não pôde ser executado e falhou. O número de erro retornado por este processo é @ERRNO@. -- 0027229ca0644181a76c4e92458afa2e Subject: Uma ou mais mensagens não puderam ser encaminhadas para o syslog Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Uma ou mais mensagens não puderam ser encaminhadas para o serviço do syslog em execução paralela ao journald. Isso normalmente indica que a implementação do syslog não foi capaz de se manter com a velocidade das mensagens enfileiradas. -- 1dee0369c7fc4736b7099b38ecb46ee7 Subject: Ponto de montagem não está vazio Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support O diretório @WHERE@ está especificado como ponto de montagem (o segundo campo no /etc/fstab ou campo Where= no arquivo de unidade do systemd) e não está vazio. Isso não interfere com a montagem, mas os arquivos pré-existentes neste diretório se tornaram inacessívels. Para ver aqueles arquivos, sobre os quais foi realizada a montagem, por favor monte manualmente o sistema de arquivos subjacente para uma localização secundária. -- 24d8d4452573402496068381a6312df2 Subject: Uma máquina virtual ou contêiner foi iniciado Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support A máquina virtual @NAME@ com seu PID @LEADER@ incial foi iniciada e está pronto para ser usad. -- 58432bd3bace477cb514b56381b8a758 Subject: Uma máquina virtual ou contêiner foi terminado Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support A máquina virtual @NAME@ com seu PID @LEADER@ incial foi desligada. PK �v�Z�ϔ��3 �3 systemd.be.catalognu �[��� # SPDX-License-Identifier: LGPL-2.1-or-later # # Message catalog for systemd's own messages # Belarusian translation # Фармат каталога апісаны на старонцы # https://www.freedesktop.org/wiki/Software/systemd/catalog # For an explanation why we do all this, see https://xkcd.com/1024/ -- f77379a8490b408bbe5f6940505a777b Subject: Сэрвіс журналявання запусціўся Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Працэс сістэмнага журналявання запусціўся, адкрыў файлы для запісу і гатовы апрацоўваць запыты. -- d93fb3c9c24d451a97cea615ce59c00b Subject: Сэрвіс журналявання спыніўся Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Працэс сістэмнага журналявання спыніўся і закрыў усе файлы. -- ec387f577b844b8fa948f33cad9a75e6 Subject: Дыскавае месца, занятае часопісам Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support @JOURNAL_NAME@ (@JOURNAL_PATH@) цяпер займае @CURRENT_USE_PRETTY@. Максімальна дазволены памер складае @MAX_USE_PRETTY@. Пакідаем вольнымі не меньш за @DISK_KEEP_FREE_PRETTY@ (даступна на дыску @DISK_AVAILABLE_PRETTY@). Такім чынам, ліміт складае @LIMIT_PRETTY@, з якіх @AVAILABLE_PRETTY@ даступна. Ліміты на памер наладжваецца з дапамогай SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= у файле /etc/systemd/journald.conf. Глядзіце journald.conf(5) для дэталей. -- a596d6fe7bfa4994828e72309e95d61e Subject: Паведамленні з сэрвісу адкінуты Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:journald.conf(5) Сэрвіс адправіў занадта штат паведамленняў за кароткі прамежак часу. Частка паведамленняў была адкінута. Майце на ўвазе, што былі адкінуты паведамлення толькі гэтага сэрвісу. Паведамленні іншых сэрвісаў засталіся. Мяжа, пасля якой паведамленні будуць адкінуты, наладжваецца з дапамогай RateLimitIntervalSec= і RateLimitBurst= у файле /etc/systemd/journald.conf. Глядзіце journald.conf(5) для дэталей. -- e9bf28e6e834481bb6f48f548ad13606 Subject: Паведамленні страчаны Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Паведамленні ядра былі страчаны, так як сістэма журналявання не паспела іх апрацаваць. -- fc2e22bc6ee647b6b90729ab34a250b1 Subject: Працэс @COREDUMP_PID@ (@COREDUMP_COMM@) скінуў дамп памяці Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:core(5) Працэс @COREDUMP_PID@ (@COREDUMP_COMM@) разбіўся і скінуў дамп памяці. Звычайна гэта сведчыць аб памылцы ў праграмным кодзе. Рэкамендуецца паведаміць аб гэтым распрацоўнікам. -- 8d45620c1a4348dbb17410da57c60c66 Subject: Новая сесія № @SESSION_ID@ створана для карыстальніка @USER_ID@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Новая сесія з № @SESSION_ID@ створана для карыстальніка @USER_ID@. Лідар гэтай сесіі пад № @LEADER@. -- 3354939424b4456d9802ca8333ed424a Subject: Сесія № @SESSION_ID@ спынена Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Сесія № @SESSION_ID@ спынена. -- fcbefc5da23d428093f97c82a9290f7b Subject: Даступна новае працоўнае месца № @SEAT_ID@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Новае працоўнае месца № @SEAT_ID@ наладжана і даступна для выкарыстання. -- e7852bfe46784ed0accde04bc864c2d5 Subject: Працоўнае месца № @SEAT_ID@ выдалена Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Працоўнае месца № @SEAT_ID@ выдалена і больш не даступна. -- c7a787079b354eaaa9e77b371893cd27 Subject: Час зменены Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Сістэмны гадзіннік зменены на @REALTIME@ мікрасекунд ад 1 студзеня 1970. -- 45f82f4aef7a4bbf942ce861d1f20990 Subject: Часавы пояс зменены на @TIMEZONE@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Сістэмны часавы пояс зменены на @TIMEZONE@. -- b07a249cd024414a82dd00cd181378ff Subject: Запуск сістэмы завяршыўся Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Усе сістэмныя сэрвісы, неабходныя для загрузкі сістэмы, паспяхова запусціліся. Майце на ўвазе, што гэта не значыць, што машына нічога не робіць. Магчыма, некаторыя сэрвісы яшчэ ініцыялізіруюцца. На запуск ядра спатрэбілася @KERNEL_USEC@ мікрасекунд. На запуск пачатковага RAM-дыска спатрэбілася @INITRD_USEC@ мікрасекунд. На запуск сістэмных сэрвісаў спатрэбілася @USERSPACE_USEC@ мікрасекунд. -- 6bbd95ee977941e497c48be27c254128 Subject: Сістэма перайшла ў стан сну @SLEEP@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Цяпер сістэма перайшла у стан сну @SLEEP@. -- 8811e6df2a8e40f58a94cea26f8ebf14 Subject: Сістэма выйшла са стана сну @SLEEP@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Цяпер сістэма выйшла са стана сну @SLEEP@. -- 98268866d1d54a499c4e98921d93bc40 Subject: Сістэма завяршае работу Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Пачаўся працэс выключэння сістэмы. Спыняюцца ўсе сістэмныя сэрвісы і дэмантуюцца файлавыя сістэмы. -- 7d4958e842da4a758f6c1cdc7b36dcc5 Subject: Юніт @UNIT@ запускаецца Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Пачаўся працэс запуску юніта @UNIT@. -- 39f53479d3a045ac8e11786248231fbf Subject: Юніт @UNIT@ запусціўся Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Працэс запуску юніта @UNIT@ завершаны. Вынік: @JOB_RESULT@. -- de5b426a63be47a7b6ac3eaac82e2f6f Subject: Юніт @UNIT@ спыняецца Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Пачаўся працэс спынення юніта @UNIT@. -- 9d1aaa27d60140bd96365438aad20286 Subject: Юніт @UNIT@ спынены Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Працэс спынення юніта @UNIT@ завершаны. -- be02cf6855d2428ba40df7e9d022f03d Subject: Збой юніта @UNIT@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Збой юніта @UNIT@. Вынік: @JOB_RESULT@. -- d34d037fff1847e6ae669a370e694725 Subject: Юніт @UNIT@ перачытвае сваю канфігурацыю Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Юніт @UNIT@ пачаў перачытваць сваю канфігурацыю. -- 7b05ebc668384222baa8881179cfda54 Subject: Юніт @UNIT@ перачытаў сваю канфігурацыю Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Юніт @UNIT@ перачытаў сваю канфігурацыю. Вынік: @JOB_RESULT@. -- 641257651c1b4ec9a8624d7a40a9e1e7 Subject: Працэс @EXECUTABLE@ не можа быць выкананы Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Працэс @EXECUTABLE@ не можа быць выкананы ў выніку збою. Ён вярнуў памылку нумар @ERRNO@. -- 0027229ca0644181a76c4e92458afa2e Sibject: Адно ці больш паведамленняў не былі накіраваны ў syslog Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Адно ці больш паведамленняў не былі накіраваны ў syslog сэрвіс, які выконваецца паралельна з journald. Звычайна гэта значыць, што рэалізацыя syslog не паспявае апрацаваць паведамленні з неабходнай хуткасцю. -- 1dee0369c7fc4736b7099b38ecb46ee7 Subject: Кропка мантавання не пустая Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Каталог @WHERE@ указаны як кропка мантавання (другое поле ў /etc/fstab ці Where= поле ў файле юніта systemd) і не пусты. Гэта не перашкаджае мантаванню, але існуючыя ў ім файлы будуць недаступны. Для доступу да іх, калі ласка, змантуйце гэтую файлавую сістэму ў іншае месца. -- 24d8d4452573402496068381a6312df2 Subject: Віртуальная машына або кантэйнер запусціўся Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Віртуальная машына @NAME@ з лідарам № @LEADER@ запусцілася і гатова для выкарыстання. -- 58432bd3bace477cb514b56381b8a758 Subject: Віртуальная машына або кантэйнер спынены Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Віртуальная машына @NAME@ з лідарам № @LEADER@ спынена. -- 36db2dfa5a9045e1bd4af5f93e1cf057 Subject: Механізм DNSSEC адключаны, бо сервер не падтымлівае яго Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) resolved.conf(5) Сэрвіс вызначэння імён (systemd-resolved.service) вызначыў, што DNS-сервер не падтрымлівае механізм DNSSEC. У выніку праверка DNSSEC была адключана. Гэтая падзея ўзнікае калі наладжаны DNSSEC=allow-downgrade у файле resolved.conf і DNS-сервер не падтрымлівае механізм DNSSEC. Звярніце ўвагу, што рэжым allow-downgrade дазваляе правесці атаку «DNSSEC downgrade», у ходзе якой зламыснік можа адключыць праверку DNSSEC шляхам падстаноўкі падробленых DNSSEC-адказаў у камунікацыйны канал. Гэта падзея можа быць прыкметай таго, што DNS-сервер сапраўды несумяшчальны з DNSSEC або што зламысніку паспяхова атрымалася правесці атаку па адключэнню DNSSEC. -- 1675d7f172174098b1108bf8c7dc8f5d Subject: Збой пры праверцы DNSSEC Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) DNS-запыт або рэсурсны запіс не прайшоў праверку DNSSEC. Як правіла, гэта паказвае на знешняе ўздзеянне на канал сувязі. -- 4d4408cfd0d144859184d1e65d7c8a65 Subject: Давераны ключ DNSSEC быў ануляваны Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) Давераны ключ DNSSEC быў ануляваны. Неабходна наладзіць новы давераны ключ або абнавіць аперацыйную сістэму, каб атрымаць абноўлены давераны ключ DNSSEC. PK �v�ZP�>b�' �' systemd.be@latin.catalognu �[��� # SPDX-License-Identifier: LGPL-2.1-or-later # # Message catalog for systemd's own messages # Belarusian Latin translation # Farmat kataloha apisany na staroncy # https://www.freedesktop.org/wiki/Software/systemd/catalog # For an explanation why we do all this, see https://xkcd.com/1024/ -- f77379a8490b408bbe5f6940505a777b Subject: Servis žurnaliavannia zapusciŭsia Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Praces sistemnaha žurnaliavannia zapusciŭsia, adkryŭ fajly dlia zapisu i hatovy apracoŭvać zapyty. -- d93fb3c9c24d451a97cea615ce59c00b Subject: Servis žurnaliavannia spyniŭsia Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Praces sistemnaha žurnaliavannia spyniŭsia i zakryŭ usie fajly. -- ec387f577b844b8fa948f33cad9a75e6 Subject: dyskavaje miesca, zaniataje časopisam Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support @JOURNAL_NAME@ (@JOURNAL_PATH@) ciapier zajmaje @CURRENT_USE_PRETTY@. Maksimaĺna dazvolieny pamier skladaje @MAX_USE_PRETTY@. Pakidajem voĺnymi nie mieńš za @DISK_KEEP_FREE_PRETTY@ (dastupna na dysku @DISK_AVAILABLE_PRETTY@). Takim čynam, limit skladaje @LIMIT_PRETTY@, z jakich @AVAILABLE_PRETTY@ dastupna. Limity na pamier naladžvaiecca z dapamohaj SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= u fajlie /etc/systemd/journald.conf. Hliadzicie journald.conf(5) dlia detaliej. -- a596d6fe7bfa4994828e72309e95d61e Subject: Paviedamlienni z servisu adkinuty Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:journald.conf(5) Servis adpraviŭ zanadta štat paviedamlienniaŭ za karotki pramiežak času. Častka paviedamlienniaŭ byla adkinuta. Majcie na ŭvazie, što byli adkinuty paviedamliennia toĺki hetaha servisu. Paviedamlienni inšych servisaŭ zastalisia. Miaža, paslia jakoj paviedamlienni buduć adkinuty, naladžvajecca z dapamohaj RateLimitIntervalSec= i RateLimitBurst= u fajlie /etc/systemd/journald.conf. Hliadzicie journald.conf(5) dlia detaliej. -- e9bf28e6e834481bb6f48f548ad13606 Subject: Paviedamlienni stračany Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Paviedamlienni jadra byli stračany, tak jak sistema žurnaliavannia nie paspiela ich apracavać. -- fc2e22bc6ee647b6b90729ab34a250b1 Subject: Praces @COREDUMP_PID@ (@COREDUMP_COMM@) skinuŭ damp pamiaci Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:core(5) Praces @COREDUMP_PID@ (@COREDUMP_COMM@) razbiŭsia i skinuŭ damp pamiaci. Zvyčajna heta sviedčyć ab pamylcy ŭ prahramnym kodzie. Rekamiendujecca paviedamić ab hetym raspracoŭnikam. -- 8d45620c1a4348dbb17410da57c60c66 Subject: Novaja siesija № @SESSION_ID@ stvorana dlia karystaĺnika @USER_ID@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Novaja siesija z № @SESSION_ID@ stvorana dlia karystaĺnika @USER_ID@. Lidar hetaj siesii pad № @LEADER@. -- 3354939424b4456d9802ca8333ed424a Subject: Siesija № @SESSION_ID@ spyniena Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Siesija № @SESSION_ID@ spyniena. -- fcbefc5da23d428093f97c82a9290f7b Subject: Dastupna novaje pracoŭnaje miesca № @SEAT_ID@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Novaje pracoŭnaje miesca № @SEAT_ID@ naladžana i dastupna dlia vykarystannia. -- e7852bfe46784ed0accde04bc864c2d5 Subject: Pracoŭnaje miesca № @SEAT_ID@ vydaliena Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) Pracoŭnaje miesca № @SEAT_ID@ vydaliena i boĺš nie dastupna. -- c7a787079b354eaaa9e77b371893cd27 Subject: Čas zmienieny Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Sistemny hadzinnik zmienieny na @REALTIME@ mikrasiekund ad 1 studzienia 1970. -- 45f82f4aef7a4bbf942ce861d1f20990 Subject: Časavy pojas zmienieny na @TIMEZONE@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Sistemny časavy pojas zmienieny na @TIMEZONE@. -- b07a249cd024414a82dd00cd181378ff Subject: Zapusk sistemy zaviaršyŭsia Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Usie sistemnyja servisy, nieabchodnyja dlia zahruzki sistemy, paspiachova zapuscilisia. Majcie na ŭvazie, što heta nie značyć, što mašyna ničoha nie robić. Mahčyma, niekatoryja servisy jašče inicyjalizirujucca. Na zapusk jadra spatrebilasia @KERNEL_USEC@ mikrasiekund. Na zapusk pačatkovaha RAM-dyska spatrebilasia @INITRD_USEC@ mikrasiekund. Na zapusk sistemnych servisaŭ spatrebilasia @USERSPACE_USEC@ mikrasiekund. -- 6bbd95ee977941e497c48be27c254128 Subject: Sistema pierajšla ŭ stan snu @SLEEP@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Ciapier sistema pierajšla u stan snu @SLEEP@. -- 8811e6df2a8e40f58a94cea26f8ebf14 Subject: Sistema vyjšla sa stana snu @SLEEP@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Ciapier sistema vyjšla sa stana snu @SLEEP@. -- 98268866d1d54a499c4e98921d93bc40 Subject: Sistema zaviaršaje rabotu Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Pačaŭsia praces vykliučennia sistemy. Spyniajucca ŭsie sistemnyja servisy i demantujucca fajlavyja sistemy. -- 7d4958e842da4a758f6c1cdc7b36dcc5 Subject: Junit @UNIT@ zapuskajecca Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Pačaŭsia praces zapusku junita @UNIT@. -- 39f53479d3a045ac8e11786248231fbf Subject: Junit @UNIT@ zapusciŭsia Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Praces zapusku junita @UNIT@ zavieršany. Vynik: @JOB_RESULT@. -- de5b426a63be47a7b6ac3eaac82e2f6f Subject: Junit @UNIT@ spyniajecca Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Pačaŭsia praces spyniennia junita @UNIT@. -- 9d1aaa27d60140bd96365438aad20286 Subject: Junit @UNIT@ spynieny Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Praces spyniennia junita @UNIT@ zavieršany. -- be02cf6855d2428ba40df7e9d022f03d Subject: Zboj junita @UNIT@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Zboj junita @UNIT@. Vynik: @JOB_RESULT@. -- d34d037fff1847e6ae669a370e694725 Subject: Junit @UNIT@ pieračytvaje svaju kanfihuracyju Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Junit @UNIT@ pačaŭ pieračytvać svaju kanfihuracyju. -- 7b05ebc668384222baa8881179cfda54 Subject: Junit @UNIT@ pieračytaŭ svaju kanfihuracyju Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Junit @UNIT@ pieračytaŭ svaju kanfihuracyju. Vynik: @JOB_RESULT@. -- 641257651c1b4ec9a8624d7a40a9e1e7 Subject: Praces @EXECUTABLE@ nie moža być vykanany Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Praces @EXECUTABLE@ nie moža być vykanany ŭ vyniku zboju. Jon viarnuŭ pamylku numar @ERRNO@. -- 0027229ca0644181a76c4e92458afa2e Sibject: Adno ci boĺš paviedamlienniaŭ nie byli nakiravany ŭ syslog Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Adno ci boĺš paviedamlienniaŭ nie byli nakiravany ŭ syslog servis, jaki vykonvajecca paralieĺna z journald. Zvyčajna heta značyć, što realizacyja syslog nie paspiavaje apracavać paviedamlienni z nieabchodnaj chutkasciu. -- 1dee0369c7fc4736b7099b38ecb46ee7 Subject: Kropka mantavannia nie pustaja Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Kataloh @WHERE@ ukazany jak kropka mantavannia (druhoje polie ŭ /etc/fstab ci Where= polie ŭ fajlie junita systemd) i nie pusty. Heta nie pieraškadžaje mantavanniu, alie isnujučyja ŭ im fajly buduć niedastupny. Dlia dostupu da ich, kali laska, zmantujcie hetuju fajlavuju sistemu ŭ inšaje miesca. -- 24d8d4452573402496068381a6312df2 Subject: Virtuaĺnaja mašyna abo kantejnier zapusciŭsia Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Virtuaĺnaja mašyna @NAME@ z lidaram № @LEADER@ zapuscilasia i hatova dlia vykarystannia. -- 58432bd3bace477cb514b56381b8a758 Subject: Virtuaĺnaja mašyna abo kantejnier spynieny Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Virtuaĺnaja mašyna @NAME@ z lidaram № @LEADER@ spyniena. -- 36db2dfa5a9045e1bd4af5f93e1cf057 Subject: Miechanizm DNSSEC adkliučany, bo siervier nie padtrymlivaje jaho Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) resolved.conf(5) Servis vyznačennia imion (systemd-resolved.service) vyznačyŭ, što DNS-siervier nie padtrymlivaje miechanizm DNSSEC. U vyniku pravierka DNSSEC byla adkliučana. Hetaja padzieja ŭznikaje kali naladžany DNSSEC=allow-downgrade u fajlie resolved.conf i DNS-siervier nie padtrymlivaje miechanizm DNSSEC. Zviarnicie ŭvahu, što režym allow-downgrade dazvaliaje praviesci ataku «DNSSEC downgrade», u chodzie jakoj zlamysnik moža adkliučyć pravierku DNSSEC šliacham padstanoŭki padroblienych DNSSEC-adkazaŭ u kamunikacyjny kanal. Heta padzieja moža być prykmietaj taho, što DNS-siervier sapraŭdy niesumiaščaĺny z DNSSEC abo što zlamysniku paspiachova atrymalasia praviesci ataku pa adkliučenniu DNSSEC. -- 1675d7f172174098b1108bf8c7dc8f5d Subject: Zboj pry praviercy DNSSEC Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) DNS-zapyt abo resursny zapis nie prajšoŭ pravierku DNSSEC. Jak pravila, heta pakazvaje na zniešniaje ŭzdziejannie na kanal suviazi. -- 4d4408cfd0d144859184d1e65d7c8a65 Subject: Davierany kliuč DNSSEC byŭ anuliavany Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) Davierany kliuč DNSSEC byŭ anuliavany. Nieabchodna naladzić novy davierany kliuč abo abnavić apieracyjnuju sistemu, kab atrymać abnoŭlieny davierany kliuč DNSSEC. PK �v�Z���23 3 dbus-broker.catalognu �[��� -- 199d4300277f495f84ba4028c984214c Subject: Falling back to resolving auxiliary groups using NSS Defined-By: dbus-broker Documentation: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/net/core/sock.c?id=28b5ba2aa0f55d80adb2624564ed2b170c19519e Support: https://groups.google.com/forum/#!forum/bus1-devel In order to determine the policy to apply to a peer we need to know the owning user as well as the users auxiliary groups. The user and group ids are provided to us by the SO_PEERCREDS sockopt, and on newer kernels we also get the auxiliary groups via the SO_PEERGROUPS sockopts. However, on older kernels where the SO_PEERGROUPS sockopt is not available, we fall back to query the auxiliary groups over NSS. This is racy as the auxiliary groups may change, and the groups we end up with may not be the ones at the time the socket was opened by the client. This is highly discouraged, and upating to a kernel with SO_PEERGROUPS support is recommended. -- 8af3357071af4153af414daae07d38e7 Subject: Dispatched @DBUS_BROKER_METRICS_DISPATCH_COUNT@ messages Defined-By: dbus-broker Support: https://groups.google.com/forum/#!forum/bus1-devel This message is printed by dbus-broker when shutting down. It includes metric information collected during the runtime of dbus-broker. The message lists the number of dispatched messages (in this case @DBUS_BROKER_METRICS_DISPATCH_COUNT@) as well as the mean time to handling a single message. The time measurements exclude the time spent on writing to and reading from the kernel. -- b209c0d9d1764ab38d13b8e00d1784d6 Subject: Peer @DBUS_BROKER_SENDER_UNIQUE_NAME@ violated the D-Bus protocol Defined-By: dbus-broker Support: https://groups.google.com/forum/#!forum/bus1-devel The peer @DBUS_BROKER_SENDER_UNIQUE_NAME@ attempted to vioalet the protocol and is therefore disconnected. -- 6fa70fa776044fa28be7a21daf42a108 Subject: Peer @DBUS_BROKER_RECEIVER_UNIQUE_NAME@ could not receive a requested message Defined-By: dbus-broker Support: https://groups.google.com/forum/#!forum/bus1-devel The peer @DBUS_BROKER_SENDER_UNIQUE_NAME@ failed to receive a message it requested and is therefore disconnected. The message in question could be a method error or reply or a broadcast the peer has subscribed to. Disconnecting the peer ensures that no messages are silently dropped. PK �v�Z�*�P �P systemd.catalognu �[��� # SPDX-License-Identifier: LGPL-2.1-or-later # Message catalog for systemd's own messages # The catalog format is documented on # https://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: https://wiki.almalinux.org/Help-and-Support 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: https://wiki.almalinux.org/Help-and-Support 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: https://wiki.almalinux.org/Help-and-Support @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: https://wiki.almalinux.org/Help-and-Support 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 or LogRateLimitIntervalSec= and LogRateLimitBurst= in the unit file. See journald.conf(5) and systemd.exec(5) for details. -- e9bf28e6e834481bb6f48f548ad13606 Subject: Journal messages have been missed Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 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: https://wiki.almalinux.org/Help-and-Support 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. -- 5aadd8e954dc4b1a8c954d63fd9e1137 Subject: Core file was truncated to @SIZE_LIMIT@ bytes. Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:coredump.conf(5) The process had more memory mapped than the configured maximum for processing and storage by systemd-coredump(8). Only the first @SIZE_LIMIT@ bytes were saved. This core might still be usable, but various tools like gdb(1) will warn about the file being truncated. -- 8d45620c1a4348dbb17410da57c60c66 Subject: A new session @SESSION_ID@ has been created for user @USER_ID@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) 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: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) A session with the ID @SESSION_ID@ has been terminated. -- fcbefc5da23d428093f97c82a9290f7b Subject: A new seat @SEAT_ID@ is now available Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) 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: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) A seat @SEAT_ID@ has been removed and is no longer available. -- c7a787079b354eaaa9e77b371893cd27 Subject: Time change Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support The system clock has been changed to @REALTIME@ microseconds after January 1st, 1970. -- 45f82f4aef7a4bbf942ce861d1f20990 Subject: Time zone change to @TIMEZONE@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support The system timezone has been changed to @TIMEZONE@. -- b07a249cd024414a82dd00cd181378ff Subject: System start-up is now complete Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support All system services necessary queued for starting at boot have been 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. Initrd start-up required @INITRD_USEC@ microseconds. Userspace start-up required @USERSPACE_USEC@ microseconds. -- eed00a68ffd84e31882105fd973abdd1 Subject: User manager start-up is now complete Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support The user manager instance for user @_UID@ has been started. All services queued for starting have been started. Note that other services might still be starting up or be started at any later time. Startup of the manager took @USERSPACE_USEC@ microseconds. -- 6bbd95ee977941e497c48be27c254128 Subject: System sleep state @SLEEP@ entered Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support The system has now entered the @SLEEP@ sleep state. -- 8811e6df2a8e40f58a94cea26f8ebf14 Subject: System sleep state @SLEEP@ left Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support The system has now left the @SLEEP@ sleep state. -- 98268866d1d54a499c4e98921d93bc40 Subject: System shutdown initiated Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support System shutdown has been initiated. The shutdown has now begun and all system services are terminated and all file systems unmounted. -- c14aaf76ec284a5fa1f105f88dfb061c Subject: System factory reset initiated Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support System factory reset has been initiated. The precise operation this executes is implementation-defined, but typically has the effect of reverting the system's state and configuration to vendor defaults. -- 7d4958e842da4a758f6c1cdc7b36dcc5 Subject: A start job for unit @UNIT@ has begun execution Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support A start job for unit @UNIT@ has begun execution. The job identifier is @JOB_ID@. -- 39f53479d3a045ac8e11786248231fbf Subject: A start job for unit @UNIT@ has finished successfully Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support A start job for unit @UNIT@ has finished successfully. The job identifier is @JOB_ID@. -- be02cf6855d2428ba40df7e9d022f03d Subject: A start job for unit @UNIT@ has failed Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support A start job for unit @UNIT@ has finished with a failure. The job identifier is @JOB_ID@ and the job result is @JOB_RESULT@. -- de5b426a63be47a7b6ac3eaac82e2f6f Subject: A stop job for unit @UNIT@ has begun execution Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support A stop job for unit @UNIT@ has begun execution. The job identifier is @JOB_ID@. -- 9d1aaa27d60140bd96365438aad20286 Subject: A stop job for unit @UNIT@ has finished Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support A stop job for unit @UNIT@ has finished. The job identifier is @JOB_ID@ and the job result is @JOB_RESULT@. -- d34d037fff1847e6ae669a370e694725 Subject: A reload job for unit @UNIT@ has begun execution Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support A reload job for unit @UNIT@ has begun execution. The job identifier is @JOB_ID@. -- 7b05ebc668384222baa8881179cfda54 Subject: A reload job for unit @UNIT@ has finished Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support A reload job for unit @UNIT@ has finished. The job identifier is @JOB_ID@ and the job result is @JOB_RESULT@. -- 641257651c1b4ec9a8624d7a40a9e1e7 Subject: Process @EXECUTABLE@ could not be executed Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 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: https://wiki.almalinux.org/Help-and-Support 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: https://wiki.almalinux.org/Help-and-Support 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: https://wiki.almalinux.org/Help-and-Support 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: https://wiki.almalinux.org/Help-and-Support 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: https://wiki.almalinux.org/Help-and-Support Documentation: man:systemd-resolved.service(8) Documentation: man: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: https://wiki.almalinux.org/Help-and-Support 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: https://wiki.almalinux.org/Help-and-Support 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. -- 5eb03494b6584870a536b337290809b3 Subject: Automatic restarting of a unit has been scheduled Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Automatic restarting of the unit @UNIT@ has been scheduled, as the result for the configured Restart= setting for the unit. -- ae8f7b866b0347b9af31fe1c80b127c0 Subject: Resources consumed by unit runtime Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support The unit @UNIT@ completed and consumed the indicated resources. -- 7ad2d189f7e94e70a38c781354912448 Subject: Unit succeeded Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support The unit @UNIT@ has successfully entered the 'dead' state. -- 0e4284a0caca4bfc81c0bb6786972673 Subject: Unit skipped Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support The unit @UNIT@ was skipped due to an ExecCondition= command failure, and has entered the 'dead' state with result '@UNIT_RESULT@'. -- d9b373ed55a64feb8242e02dbe79a49c Subject: Unit failed Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support The unit @UNIT@ has entered the 'failed' state with result '@UNIT_RESULT@'. -- 98e322203f7a4ed290d09fe03c09fe15 Subject: Unit process exited Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support An @COMMAND@= process belonging to unit @UNIT@ has exited. The process' exit code is '@EXIT_CODE@' and its exit status is @EXIT_STATUS@. -- 50876a9db00f4c40bde1a2ad381c3a1b Subject: The system is configured in a way that might cause problems Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support The following "tags" are possible: - "split-usr" — /usr is a separate file system and was not mounted when systemd was booted - "cgroups-missing" — the kernel was compiled without cgroup support or access to expected interface files is restricted - "var-run-bad" — /var/run is not a symlink to /run - "overflowuid-not-65534" — the kernel user ID used for "unknown" users (with NFS or user namespaces) is not 65534 - "overflowgid-not-65534" — the kernel group ID used for "unknown" users (with NFS or user namespaces) is not 65534 Current system is tagged as @TAINT@. -- fe6faa94e7774663a0da52717891d8ef Subject: A process of @UNIT@ unit has been killed by the OOM killer. Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support A process of unit @UNIT has been killed by the Linux kernel out-of-memory (OOM) killer logic. This usually indicates that the system is low on memory and that memory needed to be freed. A process associated with @UNIT@ has been determined as the best process to terminate and has been forcibly terminated by the kernel. Note that the memory pressure might or might not have been caused by @UNIT@. -- b61fdac612e94b9182285b998843061f Subject: Accepting user/group name @USER_GROUP_NAME@, which does not match strict user/group name rules. Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: https://systemd.io/USER_NAMES The user/group name @USER_GROUP_NAME@ has been specified, which is accepted according the relaxed user/group name rules, but does not qualify under the strict rules. The strict user/group name rules written as regular expression are: ^[a-zA-Z_][a-zA-Z0-9_-]{0,30}$ The relaxed user/group name rules accept all names, except for the empty string; names containing NUL bytes, control characters, colon or slash characters; names not valid UTF-8; names with leading or trailing whitespace; the strings "." or ".."; fully numeric strings, or strings beginning in a hyphen and otherwise fully numeric. -- 1b3bb94037f04bbf81028e135a12d293 Subject: Failed to generate valid unit name from path '@MOUNT_POINT@'. Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support The following mount point path could not be converted into a valid .mount unit name: @MOUNT_POINT@ Typically this means that the path to the mount point is longer than allowed for valid unit names. systemd dynamically synthesizes .mount units for all mount points appearing on the system. For that a simple escaping algorithm is applied: the absolute path name is used, with all "/" characters replaced by "-" (the leading one is removed). Moreover, any non-alphanumeric characters (as well as any of ":", "-", "_", ".", "\") are replaced by "\xNN" where "NN" is the hexadecimal code of the character. Finally, ".mount" is suffixed. The resulting string must be under 256 characters in length to be a valid unit name. This restriction is made in order for all unit names to also be suitable as file names. If a mount point appears that — after escaping — is longer than this limit it cannot be mapped to a unit. In this case systemd will refrain from synthesizing a unit and cannot be used to manage the mount point. It will not appear in the service manager's unit table and thus also not be torn down safely and automatically at system shutdown. It is generally recommended to avoid such overly long mount point paths, or — if used anyway – manage them independently of systemd, i.e. establish them as well as tear them down automatically at system shutdown by other software. -- b480325f9c394a7b802c231e51a2752c Subject: Special user @OFFENDING_USER@ configured, this is not safe! Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: https://systemd.io/UIDS-GIDS The unit @UNIT@ is configured to use User=@OFFENDING_USER@. This is not safe. The @OFFENDING_USER@ user's main purpose on Linux-based operating systems is to be the owner of files that otherwise cannot be mapped to any local user. It's used by the NFS client and Linux user namespacing, among others. By running a unit's processes under the identity of this user they might possibly get read and even write access to such files that cannot otherwise be mapped. It is strongly recommended to avoid running services under this user identity, in particular on systems using NFS or running containers. Allocate a user ID specific to this service, either statically via systemd-sysusers or dynamically via the DynamicUser= service setting. -- 1c0454c1bd2241e0ac6fefb4bc631433 Subject: systemd-udev-settle.service is deprecated. Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Usage of the systemd service unit systemd-udev-settle.service is deprecated. It inserts artificial delays into the boot process without providing the guarantees other subsystems traditionally assumed it provides. Relying on this service is racy, and it is generally a bug to make use of it and depend on it. Traditionally, this service's job was to wait until all devices a system possesses have been fully probed and initialized, delaying boot until this phase is completed. However, today's systems and hardware generally don't work this way anymore, hardware today may show up any time and take any time to be probed and initialized. Thus, in the general case, it's no longer possible to correctly delay boot until "all devices" have been processed, as it is not clear what "all devices" means and when they have been found. This is in particular the case if USB hardware or network-attached hardware is used. Modern software that requires some specific hardware (such as a network device or block device) to operate should only wait for the specific devices it needs to show up, and otherwise operate asynchronously initializing devices as they appear during boot and during runtime without delaying the boot process. It is a defect of the software in question if it doesn't work this way, and still pulls systemd-udev-settle.service into the boot process. Please file a bug report against the following units, with a request for it to be updated to operate in a hotplug fashion without depending on systemd-udev-settle.service: @OFFENDING_UNITS@ -- 7c8a41f37b764941a0e1780b1be2f037 Subject: Initial clock synchronization Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support For the first time during the current boot an NTP synchronization has been acquired and the local system clock adjustment has been initiated. -- 3f7d5ef3e54f4302b4f0b143bb270cab Subject: TPM PCR Extended Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support The string '@MEASURING@' has been extended into Trusted Platform Module's (TPM) Platform Configuration Register (PCR) @PCR@, on banks @BANKS@. Whenever the system transitions to a new runtime phase, a different string is extended into the specified PCR, to ensure that security policies for TPM-bound secrets and other resources are limited to specific phases of the runtime. PK �v�Z{T� � systemd.zh_TW.catalognu �[��� # SPDX-License-Identifier: LGPL-2.1-or-later # # Copyright © 2015 Jeff Huang # Message catalog for systemd's own messages # Traditional Chinese translation # Catalog 的格式記錄於 # https://www.freedesktop.org/wiki/Software/systemd/catalog # For an explanation why we do all this, see https://xkcd.com/1024/ -- f77379a8490b408bbe5f6940505a777b Subject: 日誌已開始 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 系統日誌行程已啟動，已開啟日誌 檔案供寫入並準備好對行程的要求做出回應。 -- d93fb3c9c24d451a97cea615ce59c00b Subject: 日誌已停止 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 系統日誌行程已關閉，且關閉所有目前 活躍的日誌檔案。 -- a596d6fe7bfa4994828e72309e95d61e Subject: 從服務而來的訊息已被抑制 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:journald.conf(5) 有一個服務在一個時間週期內記錄了太多訊息。 從該服務而來的訊息已被丟棄。 注意，只有有問題的服務之訊息被丟棄， 其他服務的訊息則不受影響。 可以在 /etc/systemd/journald.conf 中設定 RateLimitIntervalSec= 以及 RateLimitBurst= 來控制當訊息要開始被丟棄時的限制。參見 journald.conf(5) 以獲得更多資訊。 -- e9bf28e6e834481bb6f48f548ad13606 Subject: 日誌訊息已遺失 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 因日誌系統對核心訊息的處理不夠快速， 部份訊息已遺失。 -- fc2e22bc6ee647b6b90729ab34a250b1 Subject: 行程 @COREDUMP_PID@ (@COREDUMP_COMM@) 核心傾印 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: man:core(5) 行程 @COREDUMP_PID@ (@COREDUMP_COMM@) 當掉並核心傾印。 這通常代表了在當掉的程式中的一個程式錯誤 並需要回報錯誤給其開發者。 -- 8d45620c1a4348dbb17410da57c60c66 Subject: 新的工作階段 @SESSION_ID@ 已為使用者 @USER_ID@ 建立 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) 一個新的工作階段，ID @SESSION_ID@ 已為使用者 @USER_ID@ 建立。 這個工作階段的領導行程為 @LEADER@。 -- 3354939424b4456d9802ca8333ed424a Subject: 工作階段 @SESSION_ID@ 已結束 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) 一個工作階段，ID @SESSION_ID@ 已結束。 -- fcbefc5da23d428093f97c82a9290f7b Subject: 新的座位 @SEAT_ID@ 可用 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) 一個新的座位 @SEAT_ID@ 已被設定且現在可用。 -- e7852bfe46784ed0accde04bc864c2d5 Subject: 座位 @SEAT_ID@ 已被移除 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Documentation: sd-login(3) 座位 @SEAT_ID@ 已被移除且不再可用。 -- c7a787079b354eaaa9e77b371893cd27 Subject: 時間變更 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 系統時間已變更為1970年1月1日後 @REALTIME@ 微秒。 -- 45f82f4aef7a4bbf942ce861d1f20990 Subject: 時區變更為 @TIMEZONE@ Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 系統時區已變更為 @TIMEZONE@。 -- b07a249cd024414a82dd00cd181378ff Subject: 系統啟動已完成 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 所有開機所必要的系統服務都已成功啟動。 注意這並不代表這臺機器有空閒的時間 可以服務，可能仍忙於完成啟動。 核心啟動需要 @KERNEL_USEC@ 微秒。 初始 RAM 磁碟啟動需要 @INITRD_USEC@ 微秒。 使用者空間啟動需要 @USERSPACE_USEC@ 微秒。 -- 6bbd95ee977941e497c48be27c254128 Subject: 系統進入 @SLEEP@ 睡眠狀態 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 系統現在已進入 @SLEEP@ 睡眠狀態。 -- 8811e6df2a8e40f58a94cea26f8ebf14 Subject: 系統離開 @SLEEP@ 睡眠狀態 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 系統現在已離開 @SLEEP@ 睡眠狀態。 -- 98268866d1d54a499c4e98921d93bc40 Subject: 系統關機開始 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Systemd 關閉已經開始。關閉已開始且所有系統服務 都已結束，所有的檔案系統也都已被卸載。 -- 7d4958e842da4a758f6c1cdc7b36dcc5 Subject: 單位 @UNIT@ 已開始啟動 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 單位 @UNIT@ 已開始啟動。 -- 39f53479d3a045ac8e11786248231fbf Subject: 單位 @UNIT@ 啟動已結束 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 單位 @UNIT@ 啟動已結束。 啟動結果為 @JOB_RESULT@。 -- de5b426a63be47a7b6ac3eaac82e2f6f Subject: 單位 @UNIT@ 已開始關閉 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 單位 @UNIT@ 已開始關閉。 -- 9d1aaa27d60140bd96365438aad20286 Subject: 單位 @UNIT@ 已關閉結束 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 單位 @UNIT@ 已關閉結束。 -- be02cf6855d2428ba40df7e9d022f03d Subject: 單位 @UNIT@ 已失敗 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 單位 @UNIT@ 已失敗。 結果為 @JOB_RESULT@。 -- d34d037fff1847e6ae669a370e694725 Subject: 單位 @UNIT@ 已開始重新載入其設定 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 單位 @UNIT@ 已開始重新載入其設定 -- 7b05ebc668384222baa8881179cfda54 Subject: 單位 @UNIT@ 已結束重新載入其設定 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 單位 @UNIT@ 已結束重新載入其設定 結果為 @JOB_RESULT@。 -- 641257651c1b4ec9a8624d7a40a9e1e7 Subject: 行程 @EXECUTABLE@ 無法執行 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 行程 @EXECUTABLE@ 無法執行且失敗。 由該行程所回傳的錯誤碼為 @ERRNO@。 -- 0027229ca0644181a76c4e92458afa2e Subject: 一個或更多訊息無法被轉發到 syslog Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 一個或更多訊息無法被轉發到 syslog 服務 以及並行執行的 journald。這通常代表著 syslog 實作並無未跟上佇列中訊息 的速度。 -- 1dee0369c7fc4736b7099b38ecb46ee7 Subject: 掛載點不為空 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 目錄 @WHERE@ 被指定為掛載點（在 /etc/fstab 中的 第二欄或是在 systemd 單位檔案中的 Where= 欄位）且其不為空。 這並不會干擾掛載，但在此目錄中已存在的檔案 會變成無法存取的狀態。要檢視這些 over-mounted 的檔案， 請手動掛載下面的檔案系統到次要 位置。 -- 24d8d4452573402496068381a6312df2 Subject: 虛擬機器或容器已啟動 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 虛擬機器 @NAME@ 包含它的領導 PID @LEADER@ 現在 已經開始並已經可以使用。 -- 58432bd3bace477cb514b56381b8a758 Subject: 虛擬機器或容器已結束 Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 虛擬機器 @NAME@ 包含它的領導 PID @LEADER@ 已經 關閉。 PK �v�ZT&�*� � systemd.de.catalognu �[��� # SPDX-License-Identifier: LGPL-2.1-or-later -- fc2e22bc6ee647b6b90729ab34a250b1 Subject: Speicherabbild für Prozess @COREDUMP_PID@ (@COREDUMP_COMM@) generiert Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support 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. -- c7a787079b354eaaa9e77b371893cd27 Subject: Zeitänderung Defined-By: systemd Support: https://wiki.almalinux.org/Help-and-Support Die System-Zeit wurde geändert auf @REALTIME@ Mikrosekunden nach dem 1. Januar 1970. PK �v�Z�)z�" " systemd.zh_CN.catalognu �[��� PK �v�Z#3�{� � g dbus-broker-launch.catalognu �[��� PK �v�ZC8~�P �P G. systemd.ru.catalognu �[��� PK �v�ZG�U6�V �V < systemd.pl.catalognu �[��� PK �v�Z~����4 �4 � systemd.fr.catalognu �[��� PK �v�Z:�+:X? X? 7 systemd.it.catalognu �[��� PK �v�Zr���Ps Ps �J systemd.bg.catalognu �[��� PK �v�Z��h! ! c� systemd.pt_BR.catalognu �[��� PK �v�Z�ϔ��3 �3 �� systemd.be.catalognu �[��� PK �v�ZP�>b�' �' � systemd.be@latin.catalognu �[��� PK �v�Z���23 3 �; dbus-broker.catalognu �[��� PK �v�Z�*�P �P /E systemd.catalognu �[��� PK �v�Z{T� � A� systemd.zh_TW.catalognu �[��� PK �v�ZT&�*� � � systemd.de.catalognu �[��� PK � ��
| ver. 1.4 |
Github
|
.
| PHP 8.2.28 | Generation time: 0.02 |
proxy
|
phpinfo
|
Settings