Source strings

52 Strings 100%
Browse Translate
1,182 Words 100%
9,801 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
52 1,182 9,801
All strings Browse Translate Zen
52 1,182 9,801
Read-only strings Browse Translate Zen
1 84 583
Strings with any failing checks Browse Translate Zen
1 84 583
Failing check: Multiple failing checks Browse Translate Zen

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 trunk
Last remote commit Automatic BLFS commit based on 3ff7a891478c883722a2f0de6c83d6b02310454a a23a67f42f
Julien Lepiller authored an hour ago
Last commit in Weblate Automatic BLFS commit based on 3ff7a891478c883722a2f0de6c83d6b02310454a a23a67f42f
Julien Lepiller authored an hour ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask lfs/*/chapter09/systemd-custom.po
Translation file Not available
Last change Aug. 24, 2024, 6:56 a.m.
Last author None
13 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 52 1,182 9,801
Translated 100% 52 100% 1,182 100% 9,801
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 52 100% 1,182 100% 9,801
Failing checks 1% 1 7% 84 5% 583
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 4 changes 0 changes 0 changes 52 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 1 change 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov

Quick numbers

1,182
Hosted words
52
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Source string added
Note that the syntax for the <filename>/usr/lib/tmpfiles.d/*.conf</filename> files can be confusing. For example, the default deletion of files in the /tmp directory is located in <filename>/usr/lib/tmpfiles.d/tmp.conf</filename> with the line: <placeholder type="screen" id="0"/> The type field, q, indicates the creation of a subvolume with quotas which is really only applicable to btrfs filesystems. It references type v which in turn references type d (directory). This then creates the specified directory if it is not present and adjusts the permissions and ownership as specified. Contents of the directory will be subject to time based cleanup if the age argument is specified.
3 months ago
User avatar None

Source string added
<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.
5 months ago
User avatar None

Source string added
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.
11 months ago
User avatar None

Source string added
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.
11 months ago
User avatar None

Source string added
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.
11 months ago
User avatar None

Source string added
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.
11 months ago
User avatar None

Source string added
<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.
a year ago
User avatar None

Source string added
<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>.
a year ago
User avatar None

Source string added
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.
a year ago
User avatar None

Source string added
Long Running Processes
a year ago
Browse all translation changes