Translation Source string Target string
Linux From Scratch 12.2/chapter09_systemd-custom — French
See <ulink role='man' url='&man;systemd.unit.5'>systemd.unit(5)</ulink> manual page for more information. After creating the configuration file, run <userinput>systemctl daemon-reload</userinput> and <userinput>systemctl restart foobar</userinput> to activate the changes to a service.
Voir la page de manuel <ulink role='man' url='&man;systemd.unit.5'>systemd.unit(5)</ulink> pour plus d'informations. Après la création du fichier de configuration, exécutez <userinput>systemctl daemon-reload</userinput> et <userinput>systemctl restart foobar</userinput> pour activer les changements à un service.
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
See <ulink role='man' url='&man;systemd.unit.5'>systemd.unit(5)</ulink> manual page for more information. After creating the configuration file, run <userinput>systemctl daemon-reload</userinput> and <userinput>systemctl restart foobar</userinput> to activate the changes to a service.
Veja-se a página de manual &quot;<ulink role='man' url='&man;systemd.unit.5'>systemd.unit(5)</ulink>&quot; para mais informação. Depois de criar o arquivo de configuração, execute &quot;<userinput>systemctl daemon-reload</userinput>&quot; e &quot;<userinput>systemctl restart foobar</userinput>&quot; para ativar as mudanças para um serviço.
Linux From Scratch 12.2/chapter09_systemd-custom — English
Debugging the Boot Sequence
Debugging the Boot Sequence
Linux From Scratch 12.2/chapter09_systemd-custom — French
Debugging the Boot Sequence
Débogage de la séquence de démarrage
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
Debugging the Boot Sequence
Depurando a Sequência de Inicialização
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
Debugging the Boot Sequence
调试引导过程
Linux From Scratch 12.2/chapter09_systemd-custom — English
Rather than plain shell scripts used in SysVinit or BSD style init systems, systemd uses a unified format for different types of startup files (or units). The command <command>systemctl</command> is used to enable, disable, control state, and obtain status of unit files. Here are some examples of frequently used commands:
Rather than plain shell scripts used in SysVinit or BSD style init systems, systemd uses a unified format for different types of startup files (or units). The command <command>systemctl</command> is used to enable, disable, control state, and obtain status of unit files. Here are some examples of frequently used commands:
Linux From Scratch 12.2/chapter09_systemd-custom — French
Rather than plain shell scripts used in SysVinit or BSD style init systems, systemd uses a unified format for different types of startup files (or units). The command <command>systemctl</command> is used to enable, disable, control state, and obtain status of unit files. Here are some examples of frequently used commands:
Plutôt que des scripts shell utilisés par les systèmes d’init du style de SysVinit ou BSD, systemd utilise un format unifié pour différents types de fichiers de démarrage (ou unités). La commande <command>systemctl</command> est utilisée pour activer, désactiver, contrôler l’état et obtenir le statut d’un fichier d’unité. Voici quelques exemples de commandes fréquentes&nbsp;:
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
Rather than plain shell scripts used in SysVinit or BSD style init systems, systemd uses a unified format for different types of startup files (or units). The command <command>systemctl</command> is used to enable, disable, control state, and obtain status of unit files. Here are some examples of frequently used commands:
Em vez de scripts planos de shell usados nos sistemas de inicialização estilo SysVinit ou BSD, o systemd usa um formato unificado para tipos diferentes dos arquivos de inicialização (ou unidades). O comando <command>systemctl</command> é usado para habilitar; desabilitar; controlar estado; e obter a situação dos arquivos de unidade. Aqui estão alguns exemplos dos comandos frequentemente usados:
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
Rather than plain shell scripts used in SysVinit or BSD style init systems, systemd uses a unified format for different types of startup files (or units). The command <command>systemctl</command> is used to enable, disable, control state, and obtain status of unit files. Here are some examples of frequently used commands:
与 SysVinit 或 BSD 风格 init 系统不同，systemd 使用统一格式处理不同种类的引导文件 (或称为单元)。命令 <command>systemctl</command> 能够启用、禁用单元文件，或控制、查询单元文件的状态。以下是一些常用的命令：
Linux From Scratch 12.2/chapter09_systemd-custom — English
<command>systemctl list-units -t <replaceable>&lt;service&gt;</replaceable> [--all]</command>: lists loaded unit files of type service.
<command>systemctl list-units -t <replaceable>&lt;service&gt;</replaceable> [--all]</command>: lists loaded unit files of type service.
Linux From Scratch 12.2/chapter09_systemd-custom — French
<command>systemctl list-units -t <replaceable>&lt;service&gt;</replaceable> [--all]</command>: lists loaded unit files of type service.
<command>systemctl list-units -t <replaceable>&lt;service&gt;</replaceable> [--all]</command>: liste les fichiers d’unité chargés de type service.
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
<command>systemctl list-units -t <replaceable>&lt;service&gt;</replaceable> [--all]</command>: lists loaded unit files of type service.
<command>systemctl list-units -t <replaceable>&lt;serviço&gt;</replaceable> [--all]</command>: lista os arquivos carregados de unidade do tipo serviço.
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
<command>systemctl list-units -t <replaceable>&lt;service&gt;</replaceable> [--all]</command>: lists loaded unit files of type service.
<command>systemctl list-units -t <replaceable>&lt;service&gt;</replaceable> [--all]</command>: 列出已加载的服务 (service) 类型单元文件。
Linux From Scratch 12.2/chapter09_systemd-custom — English
<command>systemctl list-units -t <replaceable>&lt;target&gt;</replaceable> [--all]</command>: lists loaded unit files of type target.
<command>systemctl list-units -t <replaceable>&lt;target&gt;</replaceable> [--all]</command>: lists loaded unit files of type target.
Linux From Scratch 12.2/chapter09_systemd-custom — French
<command>systemctl list-units -t <replaceable>&lt;target&gt;</replaceable> [--all]</command>: lists loaded unit files of type target.
<command>systemctl list-units -t <replaceable>&lt;target&gt;</replaceable> [--all]</command>&nbsp;: liste les fichiers d’unité chargés de type target.
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
<command>systemctl list-units -t <replaceable>&lt;target&gt;</replaceable> [--all]</command>: lists loaded unit files of type target.
<command>systemctl list-units -t <replaceable>&lt;alvo&gt;</replaceable> [--all]</command>: lista os arquivos carregados de unidade do tipo alvo.
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
<command>systemctl list-units -t <replaceable>&lt;target&gt;</replaceable> [--all]</command>: lists loaded unit files of type target.
<command>systemctl list-units -t <replaceable>&lt;target&gt;</replaceable> [--all]</command>: 列出已加载的引导目标 (target) 类型单元文件。
Linux From Scratch 12.2/chapter09_systemd-custom — English
<command>systemctl show -p Wants <replaceable>&lt;multi-user.target&gt;</replaceable></command>: shows all units that depend on the multi-user target. Targets are special unit files that are analogous to runlevels under SysVinit.
<command>systemctl show -p Wants <replaceable>&lt;multi-user.target&gt;</replaceable></command>: shows all units that depend on the multi-user target. Targets are special unit files that are analogous to runlevels under SysVinit.
Linux From Scratch 12.2/chapter09_systemd-custom — French
<command>systemctl show -p Wants <replaceable>&lt;multi-user.target&gt;</replaceable></command>: shows all units that depend on the multi-user target. Targets are special unit files that are analogous to runlevels under SysVinit.
<command>systemctl show -p Wants <replaceable>&lt;multi-user.target&gt;</replaceable></command>&nbsp;: montre toutes les unités qui dépendent de la cible multi-user. Les cibles sont des fichiers d’unité spéciaux qui sont analogues aux niveaux d’exécution de SysVinit.
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
<command>systemctl show -p Wants <replaceable>&lt;multi-user.target&gt;</replaceable></command>: shows all units that depend on the multi-user target. Targets are special unit files that are analogous to runlevels under SysVinit.
<command>systemctl show -p Wants <replaceable>&lt;multi-user.target&gt;</replaceable></command>: mostra todas as unidades que dependem do alvo multi-user. Alvos são arquivos especiais de unidade que são análogos a níveis de execução sob o SysVinit.
Linux From Scratch 12.2/chapter09_systemd-custom — English
<command>systemctl status <replaceable>&lt;servicename.service&gt;</replaceable></command>: shows the status of the servicename service. The .service extension can be omitted if there are no other unit files with the same name, such as .socket files (which create a listening socket that provides similar functionality to inetd/xinetd).
<command>systemctl status <replaceable>&lt;servicename.service&gt;</replaceable></command>: shows the status of the servicename service. The .service extension can be omitted if there are no other unit files with the same name, such as .socket files (which create a listening socket that provides similar functionality to inetd/xinetd).
Linux From Scratch 12.2/chapter09_systemd-custom — French
<command>systemctl status <replaceable>&lt;servicename.service&gt;</replaceable></command>: shows the status of the servicename service. The .service extension can be omitted if there are no other unit files with the same name, such as .socket files (which create a listening socket that provides similar functionality to inetd/xinetd).
<command>systemctl status <replaceable>&lt;servicename.service&gt;</replaceable></command>&nbsp;: montre le statut du service servicename. L’extension .service peut être omise s’il n’y a pas d’autres fichiers d’unité portant le même nom, comme des fichiers .socket (qui créent un socket en écoute qui fourni les même fonctionnalités qu'inetd/xinetd).
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
<command>systemctl status <replaceable>&lt;servicename.service&gt;</replaceable></command>: shows the status of the servicename service. The .service extension can be omitted if there are no other unit files with the same name, such as .socket files (which create a listening socket that provides similar functionality to inetd/xinetd).
<command>systemctl status <replaceable>&lt;nome_serviço.service&gt;</replaceable></command>: mostra a situação do serviço nome_serviço. A extensão .service pode ser omitida se não existirem outros arquivos de unidade com o mesmo nome, tais como arquivos .socket (os quais criam um soquete de escuta que fornece funcionalidade similar ao inetd/xinetd).
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
<command>systemctl status <replaceable>&lt;servicename.service&gt;</replaceable></command>: shows the status of the servicename service. The .service extension can be omitted if there are no other unit files with the same name, such as .socket files (which create a listening socket that provides similar functionality to inetd/xinetd).
<command>systemctl status <replaceable>&lt;servicename.service&gt;</replaceable></command>: 显示名为 servicename 的服务的状态。如果没有同名的其他类型单元文件，可以省略 .service 后缀。其他类型的单元文件有 .socket 文件 (它创建一个监听套接字，提供和 inetd/xinetd 类似的功能)。
Linux From Scratch 12.2/chapter09_systemd-custom — English
Working with the Systemd Journal
Working with the Systemd Journal
Linux From Scratch 12.2/chapter09_systemd-custom — French
Working with the Systemd Journal
Utiliser le journal Systemd
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
Working with the Systemd Journal
Trabalhando com o Diário do Systemd
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
Working with the Systemd Journal
使用 systemd 日志
Linux From Scratch 12.2/chapter09_systemd-custom — English
Logging on a system booted with systemd is handled with systemd-journald (by default), rather than a typical unix syslog daemon. You can also add a normal syslog daemon and have both operate side by side if desired. The systemd-journald program stores journal entries in a binary format rather than a plain text log file. To assist with parsing the file, the command <command>journalctl</command> is provided. Here are some examples of frequently used commands:
Logging on a system booted with systemd is handled with systemd-journald (by default), rather than a typical unix syslog daemon. You can also add a normal syslog daemon and have both operate side by side if desired. The systemd-journald program stores journal entries in a binary format rather than a plain text log file. To assist with parsing the file, the command <command>journalctl</command> is provided. Here are some examples of frequently used commands:
Linux From Scratch 12.2/chapter09_systemd-custom — French
Logging on a system booted with systemd is handled with systemd-journald (by default), rather than a typical unix syslog daemon. You can also add a normal syslog daemon and have both operate side by side if desired. The systemd-journald program stores journal entries in a binary format rather than a plain text log file. To assist with parsing the file, the command <command>journalctl</command> is provided. Here are some examples of frequently used commands:
La journalisation d’un système démarré avec systemd est géré par systemd-journald (par défaut), plutôt qu’un démon syslog unix typique. Vous pouvez aussi ajouter un démon syslog normal et faire travailler les deux côte à côte si vous le souhaitez. Le programme systemd-journald stocke les entrées du journal dans un format binaire plutôt que dans un fichier en texte brut. La commande <command>journalctl</command> est fournie pour aider à analyser le fichier. Voici quelques exemples de commandes usuelles&nbsp;:
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
Logging on a system booted with systemd is handled with systemd-journald (by default), rather than a typical unix syslog daemon. You can also add a normal syslog daemon and have both operate side by side if desired. The systemd-journald program stores journal entries in a binary format rather than a plain text log file. To assist with parsing the file, the command <command>journalctl</command> is provided. Here are some examples of frequently used commands:
O registro em um sistema inicializado com o systemd é manuseado com o systemd-journald (por padrão), em vez de um processo de segundo plano típico do Unix syslog. Você também pode adicionar um processo de segundo plano normal syslog e ter ambos operando lado a lado se desejado. O aplicativo systemd-journald armazena entradas de diário em um formato binário, em vez de um arquivo plano de registro de texto. Para auxiliar na análise do arquivo, o comando <command>journalctl</command> é fornecido. Aqui estão alguns exemplos dos comandos frequentemente usados:
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
Logging on a system booted with systemd is handled with systemd-journald (by default), rather than a typical unix syslog daemon. You can also add a normal syslog daemon and have both operate side by side if desired. The systemd-journald program stores journal entries in a binary format rather than a plain text log file. To assist with parsing the file, the command <command>journalctl</command> is provided. Here are some examples of frequently used commands:
(默认情况下) 在使用 systemd 引导的系统上，systemd-journald 服务负责处理日志，它取代了传统的 Unix syslog 守护进程。如果您希望的话，也可以添加一个普通 syslog 守护进程，它和 systemd-journald 可以一起工作。systemd-journald 程序将日志项储存为二进制格式，而不是纯文本日志文件。为了解析日志文件，需要使用 systemd 提供的 <command>journalctl</command> 命令。下面是该命令的常见用法：
Linux From Scratch 12.2/chapter09_systemd-custom — English
<command>journalctl -r</command>: shows all contents of the journal in reverse chronological order.
<command>journalctl -r</command>: shows all contents of the journal in reverse chronological order.
Linux From Scratch 12.2/chapter09_systemd-custom — French
<command>journalctl -r</command>: shows all contents of the journal in reverse chronological order.
<command>journalctl -r</command>&nbsp;: montre tout le contenu du journal en sens chronologique inverse.
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
<command>journalctl -r</command>: shows all contents of the journal in reverse chronological order.
<command>journalctl -r</command>: mostra todo o conteúdo do diário em ordem cronológica reversa.
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
<command>journalctl -r</command>: shows all contents of the journal in reverse chronological order.
<command>journalctl -r</command>：按时间顺序，倒序显示所有日志内容。
Linux From Scratch 12.2/chapter09_systemd-custom — English
<command>journalctl -u <replaceable>UNIT</replaceable></command>: shows the journal entries associated with the specified UNIT file.
<command>journalctl -u <replaceable>UNIT</replaceable></command>: shows the journal entries associated with the specified UNIT file.
Linux From Scratch 12.2/chapter09_systemd-custom — French
<command>journalctl -u <replaceable>UNIT</replaceable></command>: shows the journal entries associated with the specified UNIT file.
<command>journalctl -u <replaceable>UNIT</replaceable></command>&nbsp;: montre les entrées du journal associées avec le fichier UNIT spécifié.
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
<command>journalctl -u <replaceable>UNIT</replaceable></command>: shows the journal entries associated with the specified UNIT file.
<command>journalctl -u <replaceable>UNIDADE</replaceable></command>: mostra as entradas de diário associadas com o arquivo especificado de UNIDADE.
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
<command>journalctl -u <replaceable>UNIT</replaceable></command>: shows the journal entries associated with the specified UNIT file.
<command>journalctl -u <replaceable>UNIT</replaceable></command>: 显示与给定单元文件 UNIT 关联的日志。
Linux From Scratch 12.2/chapter09_systemd-custom — English
<command>journalctl -b[=ID] -r</command>: shows the journal entries since last successful boot (or for boot ID) in reverse chronological order.
<command>journalctl -b[=ID] -r</command>: shows the journal entries since last successful boot (or for boot ID) in reverse chronological order.
Linux From Scratch 12.2/chapter09_systemd-custom — French
<command>journalctl -b[=ID] -r</command>: shows the journal entries since last successful boot (or for boot ID) in reverse chronological order.
<command>journalctl -b[=ID] -r</command>&nbsp;: montre les entrées du journal depuis le dernier démarrage réussi (ou pour le démarrage d’identifiant ID) en sens chronologique inverse.
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
<command>journalctl -b[=ID] -r</command>: shows the journal entries since last successful boot (or for boot ID) in reverse chronological order.
<command>journalctl -b[=ID] -r</command>: mostra as entradas de diário desde a mais recente inicialização bem sucedida (ou para a ID de inicialização) em ordem cronológica reversa.
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
<command>journalctl -b[=ID] -r</command>: shows the journal entries since last successful boot (or for boot ID) in reverse chronological order.
<command>journalctl -b[=ID] -r</command>: 按时间倒序，显示自上次引导以来 (或编号为 ID 的引导中) 的所有日志。
Linux From Scratch 12.2/chapter09_systemd-custom — English
<command>journalctl -f</command>: provides functionality similar to tail -f (follow).
<command>journalctl -f</command>: provides functionality similar to tail -f (follow).
Linux From Scratch 12.2/chapter09_systemd-custom — French
<command>journalctl -f</command>: provides functionality similar to tail -f (follow).
<command>journalctl -f</command>&nbsp;: fournit une fonctionnalité similaire à tail -f (suivre).
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
<command>journalctl -f</command>: provides functionality similar to tail -f (follow).
<command>journalctl -f</command>: fornece funcionalidade similar ao tail -f (seguir).
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
<command>journalctl -f</command>: provides functionality similar to tail -f (follow).
<command>journalctl -f</command>: 提供类似 tail -f 的功能 (不断将新日志项输出到屏幕)。
Linux From Scratch 12.2/chapter09_systemd-custom — English
Working with Core Dumps
Working with Core Dumps
Linux From Scratch 12.2/chapter09_systemd-custom — French
Working with Core Dumps
Travailler avec les core dumps
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
Working with Core Dumps
Trabalhando com Despejos de Núcleo
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
Working with Core Dumps
处理核心转储
Linux From Scratch 12.2/chapter09_systemd-custom — English
Core dumps are useful to debug crashed programs, especially when a daemon process crashes. On systemd booted systems the core dumping is handled by <command>systemd-coredump</command>. It will log the core dump in the journal and store the core dump itself in <filename class="directory">/var/lib/systemd/coredump</filename>. To retrieve and process core dumps, the <command>coredumpctl</command> tool is provided. Here are some examples of frequently used commands:
Core dumps are useful to debug crashed programs, especially when a daemon process crashes. On systemd booted systems the core dumping is handled by <command>systemd-coredump</command>. It will log the core dump in the journal and store the core dump itself in <filename class="directory">/var/lib/systemd/coredump</filename>. To retrieve and process core dumps, the <command>coredumpctl</command> tool is provided. Here are some examples of frequently used commands:
Linux From Scratch 12.2/chapter09_systemd-custom — French
Core dumps are useful to debug crashed programs, especially when a daemon process crashes. On systemd booted systems the core dumping is handled by <command>systemd-coredump</command>. It will log the core dump in the journal and store the core dump itself in <filename class="directory">/var/lib/systemd/coredump</filename>. To retrieve and process core dumps, the <command>coredumpctl</command> tool is provided. Here are some examples of frequently used commands:
Les «&nbsp;core dumps&nbsp;» sont utiles pour déboguer des programmes crashés, surtout quand un processus démon plante. Sur un système démarré avec systemd, les core dumps sont gérés par <command>systemd-coredump</command>. Il enregistrera le core dump das le journal et stockera le fichier core dans <filename class="directory">/var/lib/systemd/coredump</filename>. Pour récupérer et utiliser le fichier core, système fourni l'outil <command>coredumpctl</command>. Voici quelques exemples de commandes fréquentes&nbsp;:
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
Core dumps are useful to debug crashed programs, especially when a daemon process crashes. On systemd booted systems the core dumping is handled by <command>systemd-coredump</command>. It will log the core dump in the journal and store the core dump itself in <filename class="directory">/var/lib/systemd/coredump</filename>. To retrieve and process core dumps, the <command>coredumpctl</command> tool is provided. Here are some examples of frequently used commands:
Despejos de núcleo são úteis para depurar aplicativos quebrados, especialmente quando um processo de aplicativo de segundo plano quebra. Em sistemas inicializados do systemd, o despejamento de núcleo é manuseado pelo <command>systemd-coredump</command>. Ele registrará o despejo de núcleo no diário e armazenará o próprio despejo de núcleo em <filename class="directory">/var/lib/systemd/coredump</filename>. Para recuperar e processar despejos de núcleo, a ferramenta <command>coredumpctl</command> é fornecida. Aqui estão alguns exemplos de comandos frequentemente usados:
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
Core dumps are useful to debug crashed programs, especially when a daemon process crashes. On systemd booted systems the core dumping is handled by <command>systemd-coredump</command>. It will log the core dump in the journal and store the core dump itself in <filename class="directory">/var/lib/systemd/coredump</filename>. To retrieve and process core dumps, the <command>coredumpctl</command> tool is provided. Here are some examples of frequently used commands:
核心转储在调试崩溃的程序时非常有用，特别是对于守护进程崩溃的情况。在 systemd 引导的系统上，核心转储由 <command>systemd-coredump</command> 处理。它会在日志中记录核心转储，并且将核心转储文件本身存储到 <filename class="directory">/var/lib/systemd/coredump</filename> 中。如果要获取和处理核心转储文件，可以使用 <command>coredumpctl</command> 工具。下面给出它的常用命令的示例：
Linux From Scratch 12.2/chapter09_systemd-custom — English
<command>coredumpctl -r</command>: lists all core dumps in reverse chronological order.
<command>coredumpctl -r</command>: lists all core dumps in reverse chronological order.
Linux From Scratch 12.2/chapter09_systemd-custom — French
<command>coredumpctl -r</command>: lists all core dumps in reverse chronological order.
<command>coredumpctl -r</command>&nbsp;: montre tous les core dumps en ordre chronologique inverse.
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
<command>coredumpctl -r</command>: lists all core dumps in reverse chronological order.
<command>coredumpctl -r</command>: lista todos os despejos de núcleo em ordem cronológica reversa.
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
<command>coredumpctl -r</command>: lists all core dumps in reverse chronological order.
<command>coredumpctl -r</command>：按时间顺序，倒序显示所有核心转储记录。
Linux From Scratch 12.2/chapter09_systemd-custom — English
<command>coredumpctl -1 info</command>: shows the information from the last core dump.
<command>coredumpctl -1 info</command>: shows the information from the last core dump.
Linux From Scratch 12.2/chapter09_systemd-custom — French
<command>coredumpctl -1 info</command>: shows the information from the last core dump.
<command>coredumpctl -1 info</command>&nbsp;: montre les informations du dernier core dump.
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
<command>coredumpctl -1 info</command>: shows the information from the last core dump.
<command>coredumpctl -1 info</command>: mostra a informação a partir do mais recente despejo de núcleo.
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
<command>coredumpctl -1 info</command>: shows the information from the last core dump.
<command>coredumpctl -1 info</command>：显示最近一次核心转储的信息。
Linux From Scratch 12.2/chapter09_systemd-custom — English
<command>coredumpctl -1 debug</command>: loads the last core dump into <ulink url="&blfs-book;general/gdb.html">GDB</ulink>.
<command>coredumpctl -1 debug</command>: loads the last core dump into <ulink url="&blfs-book;general/gdb.html">GDB</ulink>.
Linux From Scratch 12.2/chapter09_systemd-custom — French
<command>coredumpctl -1 debug</command>: loads the last core dump into <ulink url="&blfs-book;general/gdb.html">GDB</ulink>.
<command>coredumpctl -1 debug</command>&nbsp;: charge le dernier core dump dans <ulink url="&blfs-book;general/gdb.html">GDB</ulink>.
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
<command>coredumpctl -1 debug</command>: loads the last core dump into <ulink url="&blfs-book;general/gdb.html">GDB</ulink>.
<command>coredumpctl -1 debug</command>: carrega o mais recente despejo de núcleo no <ulink url="&blfs-book;general/gdb.html">GDB</ulink>.
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
<command>coredumpctl -1 debug</command>: loads the last core dump into <ulink url="&blfs-book;general/gdb.html">GDB</ulink>.
<command>coredumpctl -1 debug</command>：将最后一次核心转储加载到 <ulink url="&blfs-book;general/gdb.html">GDB</ulink> 中。
Linux From Scratch 12.2/chapter09_systemd-custom — English
Core dumps may use a lot of disk space. The maximum disk space used by core dumps can be limited by creating a configuration file in <filename class="directory">/etc/systemd/coredump.conf.d</filename>. For example:
Core dumps may use a lot of disk space. The maximum disk space used by core dumps can be limited by creating a configuration file in <filename class="directory">/etc/systemd/coredump.conf.d</filename>. For example:
Linux From Scratch 12.2/chapter09_systemd-custom — French
Core dumps may use a lot of disk space. The maximum disk space used by core dumps can be limited by creating a configuration file in <filename class="directory">/etc/systemd/coredump.conf.d</filename>. For example:
Les core dumps peuvent utiliser beaucoup d'espace disque. L'espace disque maximal utilisé par les core dumps se limite en créant un fichier de configuration dans <filename class="directory">/etc/systemd/coredump.conf.d</filename>. Par exemple&nbsp;:
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
Core dumps may use a lot of disk space. The maximum disk space used by core dumps can be limited by creating a configuration file in <filename class="directory">/etc/systemd/coredump.conf.d</filename>. For example:
Despejos de núcleo possivelmente usem um monte de espaço em disco. O espaço máximo em disco usado por despejos de núcleo pode ser limitado criando-se um arquivo de configuração em <filename class="directory">/etc/systemd/coredump.conf.d</filename>. Por exemplo:
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
Core dumps may use a lot of disk space. The maximum disk space used by core dumps can be limited by creating a configuration file in <filename class="directory">/etc/systemd/coredump.conf.d</filename>. For example:
核心转储可能使用大量磁盘空间。为了限制核心转储使用的最大磁盘空间，可以在 <filename class="directory">/etc/systemd/coredump.conf.d</filename> 中创建一个配置文件。例如：
Linux From Scratch 12.2/chapter09_systemd-custom — English
<userinput>mkdir -pv /etc/systemd/coredump.conf.d

cat &gt; /etc/systemd/coredump.conf.d/maxuse.conf &lt;&lt; EOF
<literal>[Coredump]
MaxUse=5G</literal>
EOF</userinput>
<userinput>mkdir -pv /etc/systemd/coredump.conf.d

cat &gt; /etc/systemd/coredump.conf.d/maxuse.conf &lt;&lt; EOF
<literal>[Coredump]
MaxUse=5G</literal>
EOF</userinput>
Linux From Scratch 12.2/chapter09_systemd-custom — French
<userinput>mkdir -pv /etc/systemd/coredump.conf.d

cat &gt; /etc/systemd/coredump.conf.d/maxuse.conf &lt;&lt; EOF
<literal>[Coredump]
MaxUse=5G</literal>
EOF</userinput>
<userinput>mkdir -pv /etc/systemd/coredump.conf.d

cat &gt; /etc/systemd/coredump.conf.d/maxuse.conf &lt;&lt; EOF
<literal>[Coredump]
MaxUse=5G</literal>
EOF</userinput>
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
<userinput>mkdir -pv /etc/systemd/coredump.conf.d

cat &gt; /etc/systemd/coredump.conf.d/maxuse.conf &lt;&lt; EOF
<literal>[Coredump]
MaxUse=5G</literal>
EOF</userinput>
<userinput>mkdir -pv /etc/systemd/coredump.conf.d

cat &gt; /etc/systemd/coredump.conf.d/maxuse.conf &lt;&lt; EOF
<literal>[Coredump]
MaxUse=5G</literal>
EOF</userinput>
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
<userinput>mkdir -pv /etc/systemd/coredump.conf.d

cat &gt; /etc/systemd/coredump.conf.d/maxuse.conf &lt;&lt; EOF
<literal>[Coredump]
MaxUse=5G</literal>
EOF</userinput>
<userinput>mkdir -pv /etc/systemd/coredump.conf.d

cat &gt; /etc/systemd/coredump.conf.d/maxuse.conf &lt;&lt; EOF
<literal>[Coredump]
MaxUse=5G</literal>
EOF</userinput>
Linux From Scratch 12.2/chapter09_systemd-custom — English
See the <ulink role='man' url='&man;systemd-coredump.8'>systemd-coredump(8)</ulink>, <ulink role='man' url='&man;coredumpctl.1'>coredumpctl(1)</ulink>, and <ulink role='man' url='&man;coredump.conf.d.5'>coredump.conf.d(5)</ulink> manual pages for more information.
See the <ulink role='man' url='&man;systemd-coredump.8'>systemd-coredump(8)</ulink>, <ulink role='man' url='&man;coredumpctl.1'>coredumpctl(1)</ulink>, and <ulink role='man' url='&man;coredump.conf.d.5'>coredump.conf.d(5)</ulink> manual pages for more information.
Linux From Scratch 12.2/chapter09_systemd-custom — French
See the <ulink role='man' url='&man;systemd-coredump.8'>systemd-coredump(8)</ulink>, <ulink role='man' url='&man;coredumpctl.1'>coredumpctl(1)</ulink>, and <ulink role='man' url='&man;coredump.conf.d.5'>coredump.conf.d(5)</ulink> manual pages for more information.
Consultez les pages de manuel <ulink role='man' url='&man;systemd-coredump.8'>systemd-coredump(8)</ulink>, <ulink role='man' url='&man;coredumpctl.1'>coredumpctl(1)</ulink> et <ulink role='man' url='&man;coredump.conf.d.5'>coredump.conf.d(5)</ulink> pour plus d'information.
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
See the <ulink role='man' url='&man;systemd-coredump.8'>systemd-coredump(8)</ulink>, <ulink role='man' url='&man;coredumpctl.1'>coredumpctl(1)</ulink>, and <ulink role='man' url='&man;coredump.conf.d.5'>coredump.conf.d(5)</ulink> manual pages for more information.
Vejam-se as páginas de manual &quot;<ulink role='man' url='&man;systemd-coredump.8'>systemd-coredump(8)</ulink>&quot;; &quot;<ulink role='man' url='&man;coredumpctl.1'>coredumpctl(1)</ulink>&quot;; e &quot;<ulink role='man' url='&man;coredump.conf.d.5'>coredump.conf.d(5)</ulink>&quot; para mais informação.
Linux From Scratch 12.2/chapter09_systemd-custom — English
Long Running Processes
Long Running Processes
Linux From Scratch 12.2/chapter09_systemd-custom — French
Long Running Processes
Processus lancés durablement
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
Long Running Processes
Processos de Execução Longa
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
Long Running Processes
持续运行进程
Linux From Scratch 12.2/chapter09_systemd-custom — English
Beginning with systemd-230, all user processes are killed when a user session is ended, even if nohup is used, or the process uses the <function>daemon()</function> or <function>setsid()</function> functions. This is a deliberate change from a historically permissive environment to a more restrictive one. The new behavior may cause issues if you depend on long running programs (e.g., <command>screen</command> or <command>tmux</command>) to remain active after ending your user session. There are three ways to enable lingering processes to remain after a user session is ended.
Beginning with systemd-230, all user processes are killed when a user session is ended, even if nohup is used, or the process uses the <function>daemon()</function> or <function>setsid()</function> functions. This is a deliberate change from a historically permissive environment to a more restrictive one. The new behavior may cause issues if you depend on long running programs (e.g., <command>screen</command> or <command>tmux</command>) to remain active after ending your user session. There are three ways to enable lingering processes to remain after a user session is ended.
Linux From Scratch 12.2/chapter09_systemd-custom — French
Beginning with systemd-230, all user processes are killed when a user session is ended, even if nohup is used, or the process uses the <function>daemon()</function> or <function>setsid()</function> functions. This is a deliberate change from a historically permissive environment to a more restrictive one. The new behavior may cause issues if you depend on long running programs (e.g., <command>screen</command> or <command>tmux</command>) to remain active after ending your user session. There are three ways to enable lingering processes to remain after a user session is ended.
Depuis la version systemd-230, tous les processus utilisateurs sont tués lorsque la session utilisateur se termine, même en utilisant nohup, ou que le processus utilise les fonctions <function>daemon()</function> ou <function>setsid()</function>. Ceci est un changement délibéré par rapport à un environnement historiquement plus permissif vers un environnement plus restrictif. Le nouveau comportement peut causer des problèmes si vous dépendez de programmes lancés durablement (par exemple, <command>screen</command> ou <command>tmux</command>) qui restent actifs après la fin de votre session utilisateur. Il y a trois moyens de permettre la persistance des processus après la fin d'une session utilisateur.
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
Beginning with systemd-230, all user processes are killed when a user session is ended, even if nohup is used, or the process uses the <function>daemon()</function> or <function>setsid()</function> functions. This is a deliberate change from a historically permissive environment to a more restrictive one. The new behavior may cause issues if you depend on long running programs (e.g., <command>screen</command> or <command>tmux</command>) to remain active after ending your user session. There are three ways to enable lingering processes to remain after a user session is ended.
Iniciando com o systemd-230, todos os processos de usuário(a) são finalizados quando uma sessão de usuário(a) for terminada, mesmo se nohup for usado ou o processo usar as funções <function>daemon()</function> ou <function>setsid()</function>. Isso é uma mudança deliberada de um ambiente historicamente permissivo para um mais restritivo. O novo comportamento possivelmente cause problemas se você depender de aplicativos de execução longa (por exemplo, <command>screen</command> ou <command>tmux</command>) para continuarem ativos depois de terminar sua sessão de usuário(a). Existem três maneiras de habilitar processos persistentes para continuarem depois que uma sessão de usuário(a) for terminada.
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
Beginning with systemd-230, all user processes are killed when a user session is ended, even if nohup is used, or the process uses the <function>daemon()</function> or <function>setsid()</function> functions. This is a deliberate change from a historically permissive environment to a more restrictive one. The new behavior may cause issues if you depend on long running programs (e.g., <command>screen</command> or <command>tmux</command>) to remain active after ending your user session. There are three ways to enable lingering processes to remain after a user session is ended.
从 systemd 的 230 版本开始，在用户会话结束时，所有用户进程都被杀死，即使使用了 nohup 或 <function>daemon()</function> 、<function>setsid</function> 等函数也不例外。这是开发者有意做出的修改，将传统的宽松环境改为更加严格的环境。如果您需要让持续运行的程序 (例如 <command>screen</command> 或 <command>tmux</command>) 在用户会话结束后保持运行，这项新的行为会导致问题。有三种方法使得这类驻留进程在用户会话结束后继续运行：
Linux From Scratch 12.2/chapter09_systemd-custom — English
<emphasis>Enable process lingering for only selected users</emphasis>: Normal users have permission to enable process lingering with the command <command>loginctl enable-linger</command> for their own user. System administrators can use the same command with a <parameter>user</parameter> argument to enable for a user. That user can then use the <command>systemd-run</command> command to start long running processes. For example: <command>systemd-run --scope --user /usr/bin/screen</command>. If you enable lingering for your user, the user@.service will remain even after all login sessions are closed, and will automatically start at system boot. This has the advantage of explicitly allowing and disallowing processes to run after the user session has ended, but breaks backwards compatibility with tools like <command>nohup</command> and utilities that use <function>daemon()</function>.
<emphasis>Enable process lingering for only selected users</emphasis>: Normal users have permission to enable process lingering with the command <command>loginctl enable-linger</command> for their own user. System administrators can use the same command with a <parameter>user</parameter> argument to enable for a user. That user can then use the <command>systemd-run</command> command to start long running processes. For example: <command>systemd-run --scope --user /usr/bin/screen</command>. If you enable lingering for your user, the user@.service will remain even after all login sessions are closed, and will automatically start at system boot. This has the advantage of explicitly allowing and disallowing processes to run after the user session has ended, but breaks backwards compatibility with tools like <command>nohup</command> and utilities that use <function>daemon()</function>.
Linux From Scratch 12.2/chapter09_systemd-custom — French
<emphasis>Enable process lingering for only selected users</emphasis>: Normal users have permission to enable process lingering with the command <command>loginctl enable-linger</command> for their own user. System administrators can use the same command with a <parameter>user</parameter> argument to enable for a user. That user can then use the <command>systemd-run</command> command to start long running processes. For example: <command>systemd-run --scope --user /usr/bin/screen</command>. If you enable lingering for your user, the user@.service will remain even after all login sessions are closed, and will automatically start at system boot. This has the advantage of explicitly allowing and disallowing processes to run after the user session has ended, but breaks backwards compatibility with tools like <command>nohup</command> and utilities that use <function>daemon()</function>.
<emphasis>N'activez les processus persistants que pour les utilisateurs qui en ont besoin</emphasis>&nbsp;: les utilisateurs ont la possibilité d'activer les processus persistants avec la commande <command>loginctl enable-linger</command> pour eux-mêmes. Les administrateurs systèmes peuvent utiliser la même commande avec un argument <parameter>utilisateur</parameter> pour les activer pour un utilisateur. Cet utilisateur peut alors utiliser la commande <command>systemd-run</command> pour débuter une tâche durable. Par exemple&nbsp;: <command>systemd-run --scope --user /usr/bin/screen</command>. Si vous souhaitez activer les tâches durables pour votre utilisateur, le service user@.service sera toujours présent même après la fermeture de toutes les sessions, et démarrera automatiquement au démarrage du système. Ceci a l'avantage d'autoriser et d'interdire explicitement aux programmes de s'exécuter après que la session utilisateur est fermée, mais cela casse la rétro-compatibilité avec des outils comme <command>nohup</command> et les utilitaires qui utilisent <function>daemon()</function>.
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
<emphasis>Enable process lingering for only selected users</emphasis>: Normal users have permission to enable process lingering with the command <command>loginctl enable-linger</command> for their own user. System administrators can use the same command with a <parameter>user</parameter> argument to enable for a user. That user can then use the <command>systemd-run</command> command to start long running processes. For example: <command>systemd-run --scope --user /usr/bin/screen</command>. If you enable lingering for your user, the user@.service will remain even after all login sessions are closed, and will automatically start at system boot. This has the advantage of explicitly allowing and disallowing processes to run after the user session has ended, but breaks backwards compatibility with tools like <command>nohup</command> and utilities that use <function>daemon()</function>.
<emphasis>Habilitar persistência de processo somente para usuários(as) selecionados(as)</emphasis>: Usuários(as) normais tem permissão para habilitar persistência de processo com o comando <command>loginctl enable-linger</command> para os(as) próprios(as) usuários(as) deles(as). Administradores(as) do sistema podem usar o mesmo comando com um argumento <parameter>user</parameter> ao habilitar para um(a) usuário(a). Esse(a) usuário(a) consegue então usar o comando <command>systemd-run</command> para iniciar processos de execução longa. Por exemplo: <command>systemd-run --scope --user /usr/bin/screen</command>. Se você habilitar a persistência para seu(ua) usuário(a), [então] a user@.service continuará, mesmo depois que todas as sessões de login forem fechadas e automaticamente iniciará na inicialização do sistema. Isso tem a vantagem de explicitamente permitir e proibir processos para execução depois que a sessão de usuário(a) tenha terminado, porém quebra retrocompatibilidade com ferramentas como <command>nohup</command> e utilitários que usam <function>daemon()</function>.
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
<emphasis>Enable process lingering for only selected users</emphasis>: Normal users have permission to enable process lingering with the command <command>loginctl enable-linger</command> for their own user. System administrators can use the same command with a <parameter>user</parameter> argument to enable for a user. That user can then use the <command>systemd-run</command> command to start long running processes. For example: <command>systemd-run --scope --user /usr/bin/screen</command>. If you enable lingering for your user, the user@.service will remain even after all login sessions are closed, and will automatically start at system boot. This has the advantage of explicitly allowing and disallowing processes to run after the user session has ended, but breaks backwards compatibility with tools like <command>nohup</command> and utilities that use <function>daemon()</function>.
<emphasis>仅为选定的用户启用进程驻留</emphasis>：普通用户有执行命令 <command>loginctl enable-linger</command> 启用进程驻留的权限，管理员可以使用带 <parameter>user</parameter> 参数的该命令，为特定用户启用进程驻留。在启用进程驻留后，可以使用 <command>systemd-run</command> 命令启动持续运行的进程。例如，<command>systemd-run --scope --user /usr/bin/screen</command>。如果您为您的用户启用了进程驻留，则 user@.service 将持续运行，甚至在所有登录会话关闭后仍然运行，而且会在系统引导时自动启动。这种方法的好处是可以显式地允许或禁止进程在用户会话结束后继续运行，但却破坏了和 <command>nohup</command> 等工具，和使用 <function>daemon()</function> 函数的工具的兼容性。
Linux From Scratch 12.2/chapter09_systemd-custom — English
<emphasis>Enable system-wide process lingering</emphasis>: You can set <parameter>KillUserProcesses=no</parameter> in <filename>/etc/systemd/logind.conf</filename> to enable process lingering globally for all users. This has the benefit of leaving the old method available to all users at the expense of explicit control.
<emphasis>Enable system-wide process lingering</emphasis>: You can set <parameter>KillUserProcesses=no</parameter> in <filename>/etc/systemd/logind.conf</filename> to enable process lingering globally for all users. This has the benefit of leaving the old method available to all users at the expense of explicit control.
Linux From Scratch 12.2/chapter09_systemd-custom — French
<emphasis>Enable system-wide process lingering</emphasis>: You can set <parameter>KillUserProcesses=no</parameter> in <filename>/etc/systemd/logind.conf</filename> to enable process lingering globally for all users. This has the benefit of leaving the old method available to all users at the expense of explicit control.
<emphasis>Activer les processus persistant sur tout le système</emphasis>&nbsp;: vous pouvez définir <parameter>KillUserProcesses=no</parameter> dans <filename>/etc/systemd/logind.conf</filename> pour autoriser globalement la persistance pour tous les utilisateurs. Ceci a l'avantage de laisser disponibles les vieilles méthodes à tous les utilisateurs au prix de la perte de contrôle explicite.
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
<emphasis>Enable system-wide process lingering</emphasis>: You can set <parameter>KillUserProcesses=no</parameter> in <filename>/etc/systemd/logind.conf</filename> to enable process lingering globally for all users. This has the benefit of leaving the old method available to all users at the expense of explicit control.
<emphasis>Habilitar persistência de processo abrangente ao sistema</emphasis>: Você pode configurar <parameter>KillUserProcesses=no</parameter> em <filename>/etc/systemd/logind.conf</filename> para habilitar a persistência de processo globalmente para todos(as) os(as) usuários(as). Isso tem o benefício de deixar o método antigo disponível para todos(as) os(as) usuários(as) à custa do controle explícito.
Linux From Scratch 12.2/chapter09_systemd-custom — Chinese (Simplified Han script)
<emphasis>Enable system-wide process lingering</emphasis>: You can set <parameter>KillUserProcesses=no</parameter> in <filename>/etc/systemd/logind.conf</filename> to enable process lingering globally for all users. This has the benefit of leaving the old method available to all users at the expense of explicit control.
<emphasis>为整个系统启用进程驻留</emphasis>：您可以在将<parameter>KillUserProcesses=no</parameter> 设置行加入 <filename>/etc/systemd/logind.conf</filename>，为所有用户全局地启用进程驻留。它的好处是允许所有用户继续使用旧方法，但无法进行明确控制。
Linux From Scratch 12.2/chapter09_systemd-custom — English
<emphasis>Disable at build-time</emphasis>: You can disable lingering by default while building systemd by adding the switch <parameter>-D default-kill-user-processes=false</parameter> to the <command>meson</command> command for systemd. This completely disables the ability of systemd to kill user processes at session end.
<emphasis>Disable at build-time</emphasis>: You can disable lingering by default while building systemd by adding the switch <parameter>-D default-kill-user-processes=false</parameter> to the <command>meson</command> command for systemd. This completely disables the ability of systemd to kill user processes at session end.
Linux From Scratch 12.2/chapter09_systemd-custom — French
<emphasis>Disable at build-time</emphasis>: You can disable lingering by default while building systemd by adding the switch <parameter>-D default-kill-user-processes=false</parameter> to the <command>meson</command> command for systemd. This completely disables the ability of systemd to kill user processes at session end.
<emphasis>Désactiver à la construction</emphasis>&nbsp;: vous pouvez autoriser les processus persistants par défaut pendant la construction de systemd en ajoutant le paramètre <parameter>-D default-kill-user-processes=false</parameter> à la commande <command>meson</command> de systemd. Ceci désactive complètement la capacité que systemd a de tuer les processus utilisateurs à la fin de la session.
Linux From Scratch 12.2/chapter09_systemd-custom — Portuguese (Brazil)
<emphasis>Disable at build-time</emphasis>: You can disable lingering by default while building systemd by adding the switch <parameter>-D default-kill-user-processes=false</parameter> to the <command>meson</command> command for systemd. This completely disables the ability of systemd to kill user processes at session end.
<emphasis>Desabilitar em tempo de construção</emphasis>: Você pode desabilitar a persistência por padrão enquanto construir o systemd adicionando a chave <parameter>-D default-kill-user-processes=false</parameter> ao comando <command>meson</command> para o systemd. Isso desabilita completamente a habilidade do systemd para finalizar processos de usuário(a) ao fim da sessão.