Zen

Translation

type: Content of: <sect1><sect2><para>
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.
275/5830 · 583

Sign in to save the translation.

English Chinese (Simplified) Actions
Working with the Systemd Journal
使用 systemd 日志
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> 命令。下面是该命令的常见用法：
<command>journalctl -r</command>: shows all contents of the journal in reverse chronological order.
<command>journalctl -r</command>：按时间顺序，倒序显示所有日志内容。
<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 关联的日志。
<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 的引导中) 的所有日志。
<command>journalctl -f</command>: provides functionality similar to tail -f (follow).
<command>journalctl -f</command>: 提供类似 tail -f 的功能 (不断将新日志项输出到屏幕)。
Working with Core Dumps
处理核心转储
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> 工具。下面给出它的常用命令的示例：
<command>coredumpctl -r</command>: lists all core dumps in reverse chronological order.
<command>coredumpctl -r</command>：按时间顺序，倒序显示所有核心转储记录。
<command>coredumpctl -1 info</command>: shows the information from the last core dump.
<command>coredumpctl -1 info</command>：显示最近一次核心转储的信息。
<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> 中。
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> 中创建一个配置文件。例如：
<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>
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.
参阅 man 手册页面 <filename>systemd-coredump(8)</filename>，<filename>coredumpctl(1)</filename>，以及 <filename>coredump.conf.d(5)</filename> 了解更多信息。
Long Running Processes
持续运行进程
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>) 在用户会话结束后保持运行，这项新的行为会导致问题。有三种方法使得这类驻留进程在用户会话结束后继续运行：
<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> 函数的工具的兼容性。
<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>，为所有用户全局地启用进程驻留。它的好处是允许所有用户继续使用旧方法，但无法进行明确控制。
<emphasis>Disable at build-time</emphasis>: You can disable lingering by default while building systemd by adding the switch <parameter>-Ddefault-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>在编译时禁用该功能</emphasis>：您可以在构建 systemd 时传递参数 <parameter>-Ddefault-kill-user-process=no</parameter> 给 <command>meson</command>，使得 systemd 默认启用进程驻留。这完全禁用了 systemd 在会话结束时杀死用户进程的功能。

Loading…

User avatar None

String updated in the repository

  1. Linux From Scratch
  2. chapter09_systemd-custom
  3. Chinese (Simplified)
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>) 在用户会话结束后保持运行，这项新的行为会导致问题。有三种方法使得这类驻留进程在用户会话结束后继续运行：
3 months ago
User avatar None

String updated in the repository

  1. Linux From Scratch
  2. chapter09_systemd-custom
  3. Chinese (Simplified)
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>) 在用户会话结束后保持运行，这项新的行为会导致问题。有三种方法使得这类驻留进程在用户会话结束后继续运行：
a year ago
Browse all string changes

Things to check

Mismatched colon

Source and translation do not both end with a colon

Reset

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Glossary

English Chinese (Simplified)
No related strings found in the glossary.

String information

Source string description
type: Content of: <sect1><sect2><para>
Flags
xml-text
Source string location
lfs-en/chapter09/systemd-custom.xml:266
String age
a year ago
Last updated
3 months ago
Source string age
a year ago
Translation file
lfs/zh_CN/chapter09/systemd-custom.po, string 49