Overview

Project website www.linuxfromscratch.org
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@git.linuxfromscratch.org:fr-lfs
Repository branch 11.3
Last remote commit Update translations for 11.3 6bfb71d1dc
Julien Lepiller authored a year ago
Last commit in Weblate Translated using Weblate (Portuguese (Brazil)) d3c469005f
User avatar jamenson authored a year ago
Weblate repository https://translate.linuxfromscratch.org/git/linux-from-scratch-11-3/index/
File mask lfs/*/chapter09/systemd-custom.po
Translation file Download lfs/zh_CN/chapter09/systemd-custom.po
Last change March 10, 2023, 5:53 p.m.
Last author None
3 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 52 1,167 9,596
Translated 94% 49 94% 1,102 94% 9,042
Needs editing 5% 3 5% 65 5% 554
Read-only 0% 0 0% 0 0% 0
Failing checks 3% 2 8% 102 7% 741
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 57 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

1,167
Hosted words
52
Hosted strings
94%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+94%
—
Contributors
—
User avatar None

Resource updated
File “lfs/zh_CN/chapter09/systemd-custom.po” was added. a year ago
User avatar None

String updated in the repository
<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 在会话结束时杀死用户进程的功能。
a year ago
User avatar None

String updated in the repository
<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>，为所有用户全局地启用进程驻留。它的好处是允许所有用户继续使用旧方法，但无法进行明确控制。
a year ago
User avatar None

String updated in the repository
<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> 函数的工具的兼容性。
a year ago
User avatar None

String updated in the repository
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
User avatar None

String updated in the repository
Long Running Processes
持续运行进程
a year ago
User avatar None

String updated in the repository
See the <filename>systemd-coredump(8)</filename>, <filename>coredumpctl(1)</filename>, and <filename>coredump.conf.d(5)</filename> manual pages for more information.
参阅 man 手册页面 <filename>systemd-coredump(8)</filename>，<filename>coredumpctl(1)</filename>，以及 <filename>coredump.conf.d(5)</filename> 了解更多信息。
a year ago
User avatar None

String updated in the repository
<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>
a year ago
User avatar None

String updated in the repository
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> 中创建一个配置文件。例如：
a year ago
User avatar None

String updated in the repository
<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> 中。
a year ago
Browse all translation changes