Translation status

52 Strings 100%
Browse Translate
1,167 Words 100%
9,596 Characters 100%

Strings status

Strings Words Characters
52 1,167 9,596
All strings Browse Translate Zen
52 1,167 9,596
Translated strings Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
chapter08_groff 0 0 0 0 0 0 0
index CC-BY-NC-2.0 0 0 0 0 0 0 0
chapter08_file 0 0 0 0 0 0 0
chapter08_libcap 0 0 0 0 0 0 0
chapter07_cleanup 0 0 0 0 0 0 0
chapter08_iana-etc 0 0 0 0 0 0 0
chapter10_kernel 0 0 0 0 0 0 0
chapter08_libffi 0 0 0 0 0 0 0
chapter08_util-linux 0 0 0 0 0 0 0
chapter08_perl 0 0 0 0 0 0 0
Browse all components

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 12.0
Last remote commit Add Portuguese (Brazil) BLFS 5a031b636f
Julien Lepiller authored a month ago
Last commit in Weblate Translated using Weblate (French) f1a0442a45
Weblate Admin authored 6 months ago
Weblate repository https://translate.linuxfromscratch.org/git/linux-from-scratch-12-0/index/
File mask lfs/*/chapter09/systemd-custom.po
Translation file Download lfs/pt_BR/chapter09/systemd-custom.po
Last change None
Last author None
yesterday

String statistics

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

Quick numbers

1,167
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

Resource updated

  1. Linux From Scratch 12.0
  2. chapter09_systemd-custom
  3. Portuguese (Brazil)
File lfs/pt_BR/chapter09/systemd-custom.po was added. 8 months ago
User avatar None

String updated in the repository

  1. Linux From Scratch 12.0
  2. chapter09_systemd-custom
  3. Portuguese (Brazil)
<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>Desabilitar em tempo de construção</emphasis>: Você pode desabilitar a persistência por padrão enquanto construir o systemd adicionando a chave <parameter>-Ddefault-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.
8 months ago
User avatar None

String updated in the repository

  1. Linux From Scratch 12.0
  2. chapter09_systemd-custom
  3. 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.
8 months ago
User avatar None

String updated in the repository

  1. Linux From Scratch 12.0
  2. chapter09_systemd-custom
  3. 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>.
8 months ago
User avatar None

String updated in the repository

  1. Linux From Scratch 12.0
  2. chapter09_systemd-custom
  3. 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.
8 months ago
User avatar None

String updated in the repository

  1. Linux From Scratch 12.0
  2. chapter09_systemd-custom
  3. Portuguese (Brazil)
Long Running Processes
Processos de Execução Longa
8 months ago
User avatar None

String updated in the repository

  1. Linux From Scratch 12.0
  2. chapter09_systemd-custom
  3. Portuguese (Brazil)
See the <filename>systemd-coredump(8)</filename>, <filename>coredumpctl(1)</filename>, and <filename>coredump.conf.d(5)</filename> manual pages for more information.
Vejam-se as páginas de manual <filename>systemd-coredump(8)</filename>; <filename>coredumpctl(1)</filename>; e <filename>coredump.conf.d(5)</filename> para mais informação.
8 months ago
User avatar None

String updated in the repository

  1. Linux From Scratch 12.0
  2. chapter09_systemd-custom
  3. 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>
8 months ago
User avatar None

String updated in the repository

  1. Linux From Scratch 12.0
  2. chapter09_systemd-custom
  3. 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:
8 months ago
User avatar None

String updated in the repository

  1. Linux From Scratch 12.0
  2. chapter09_systemd-custom
  3. 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>.
8 months ago
Browse all translation changes