6 strings / 243 words

Translation Source string Target string
Linux From Scratch 12.3/chapter09_systemd-custom — Chinese (Simplified Han script)
The <filename>/etc/systemd/system.conf</filename> file contains a set of options to control basic systemd operations. The default file has all entries commented out with the default settings indicated. This file is where the log level may be changed as well as some basic logging settings. See the <ulink role='man' url='&man;systemd-system.conf.5'>systemd-system.conf(5)</ulink> manual page for details on each configuration option.
<filename>/etc/systemd/system.conf</filename> 文件包含一组控制 systemd 基本功能的选项。默认文件中所有条目都被注释掉，并标明了默认值。可以在这里修改日志级别，以及其他一些基本日志设定。参阅 <filename>systemd-system.conf(5)</filename> man 手册页面了解每个选项的详细信息。
Linux From Scratch 12.3/chapter09_systemd-custom — Chinese (Simplified Han script)
The boot messages can always be reviewed by using the <userinput>journalctl -b</userinput> command as the <systemitem class="username">root</systemitem> user.
您总是可以用 root 身份运行 <userinput>journalctl -b</userinput> 命令，查阅引导消息。
Linux From Scratch 12.3/chapter09_systemd-custom — Chinese (Simplified Han script)
The system location for the configuration files is <filename>/usr/lib/tmpfiles.d/*.conf</filename>. The local configuration files are in <filename class="directory">/etc/tmpfiles.d</filename>. Files in <filename class="directory">/etc/tmpfiles.d</filename> override files with the same name in <filename class="directory">/usr/lib/tmpfiles.d</filename>. See <ulink role='man' url='&man;tmpfiles.d.5'>tmpfiles.d(5)</ulink> manual page for file format details.
它们的系统配置文件位于 <filename>/usr/lib/tmpfiles.d/*.conf</filename>。本地配置文件位于 <filename class="directory">/etc/tmpfiles.d</filename>。<filename class="directory">/etc/tmpfiles.d</filename> 中的文件覆盖 <filename class="directory">/usr/lib/tmpfiles.d</filename> 中的同名文件。参阅 <filename>tmpfiles.d(5)</filename> man 手册页面，了解配置文件格式的细节。
Linux From Scratch 12.3/chapter09_systemd-custom — Chinese (Simplified Han script)
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.
参阅 <filename>systemd.unit(5)</filename> man 手册页面获取更多信息。在创建配置文件后，执行 <userinput>systemctl daemon-reload</userinput> 和 <userinput>systemctl restart foobar</userinput>，激活对服务进行的修改。
Linux From Scratch 12.3/chapter09_systemd-custom — Chinese (Simplified Han script)
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> 了解更多信息。
Linux From Scratch 12.3/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>) 在用户会话结束后保持运行，这项新的行为会导致问题。有三种方法使得这类驻留进程在用户会话结束后继续运行：