fedora-docs-l10n/fedora-coreos/master/pages/debugging-kernel-crashes — Portuguese (Brazil) @ Fedora Weblate: sudo rpm-ostree kargs --append='crashkernel=300M'

Zen

Translation

English type: delimited block -

Portuguese (Brazil)

Needs editing

Skip

	English	Portuguese (Brazil)	Actions
	Debugging kernel crashes using kdump	Depurando falhas do kernel usando o kdump
	Introduction	Introdução
	kdump is a service that creates crash dumps when there is a kernel crash. It uses https://www.mankier.com/8/kexec[`kexec(8)`] to boot into a secondary kernel (known as a capture kernel), then exports the contents of the kernel's memory (known as a crash dump or vmcore) to the filesystem. The contents of vmcore can then be analyzed to root cause the kernel crash.	kdump é um serviço que cria um "crash dump" ou "despejo de erros" quando há uma falha no kernel. Ele usa https://www.mankier.com/8/kexec[`kexec(8)`] para inicializar em um kernel secundário (conhecido como kernel de captura) e, em seguida, exporta o conteúdo da memória do kernel (conhecido como crash dump ou vmcore) para o sistema de arquivos. O conteúdo do vmcore pode então ser analisado para determinar a raiz da falha do kernel.
	Configuring kdump requires setting the `crashkernel` kernel argument and enabling the kdump systemd service. Memory must be reserved for the crash kernel during booting of the first kernel. `crashkernel=auto` generally doesn't reserve enough memory on Fedora CoreOS, so it is recommended to specify `crashkernel=300M`.	A configuração do kdump requer a definição do argumento do kernel `crashkernel` e a ativação do serviço systemd kdump. A memória deve ser reservada para o kernel travado durante a inicialização do primeiro kernel. `crashkernel=auto` geralmente não reserva memória suficiente no Fedora CoreOS, então é recomendado especificar `crashkernel=300M`.
	By default, the vmcore will be saved in `/var/crash`. It is also possible to write the dump to some other location on the local system or to send it over the network by editing `/etc/kdump.conf`. For additional information, see https://www.mankier.com/5/kdump.conf[`kdump.conf(5)`] and the comments in `/etc/kdump.conf` and `/etc/sysconfig/kdump`.	Por padrão, o vmcore será salvo em `/var/crash`. Também é possível gravar o dump em algum outro espaço no sistema local ou enviá-lo pela rede editando `/etc/kdump.conf`. Para obter informações adicionais, consulte https://www.mankier.com/5/kdump.conf[`kdump.conf(5)`] e os comentários em `/etc/kdump.conf` e `/etc/sysconfig/kdump`.
	Configuring kdump via Ignition	Configurando o kdump via Ignition
	Example kdump configuration	Exemplo de configuração do kdump
	variant: fcos version: {butane-latest-stable-spec} kernel_arguments: should_exist: - 'crashkernel=300M' systemd: units: - name: kdump.service enabled: true
	Configuring kdump after initial provision	Configurando o kdump após o provisionamento inicial
	Set the crashkernel kernel argument	Defina o argumento de kernel crashkernel
	sudo rpm-ostree kargs --append='crashkernel=300M'	sudo rpm-ostree kargs --append='crashkernel=300M'
	xref:kernel-args.adoc[More information] on how to modify kargs via `rpm-ostree`.	xref:kernel-args.adoc[Mais informações] sobre como modificar kargs via `rpm-ostree`.
	Enable the kdump systemd service.	Habilite o serviço systemd kdump.
	sudo systemctl enable kdump.service	sudo systemctl enable kdump.service
	Reboot your system.	Reinicialize seu sistema.
	sudo systemctl reboot	sudo systemctl reboot
	It is highly recommended to test the configuration after setting up the `kdump` service, with extra attention to the amount of memory reserved for the crash kernel. For information on how to test that kdump is properly armed and how to analyze the dump, refer to the https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes[kdump documentation for Fedora] and https://www.kernel.org/doc/html/latest/admin-guide/kdump/kdump.html[the Linux kernel documentation on kdump].	É altamente recomendável testar a configuração após configurar o serviço `kdump`, com atenção extra para a quantidade de memória reservada para o kernel de travamento. Para informações sobre como testar se o kdump está devidamente armado e como analisar o despejo, consulte a https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes[documentação de kdump para Fedora] e https://www.kernel.org/doc/html/latest/admin-guide/kdump/kdump.html[a documentação do kernel Linux sobre kdump].

Loading…

None String updated in the repository fedora-docs-l10n/fedora-coreos master/pages/debugging-kernel-crashes Portuguese (Brazil)	English sudo rpm-ostree kargs --append='crashkernel=300M' Portuguese (Brazil) 0 characters edited Current translation Translated sudo rpm-ostree kargs --append='crashkernel=300M' 2 years ago
rffontenelle Suggestion removed fedora-docs-l10n/fedora-coreos master/pages/debugging-kernel-crashes Portuguese (Brazil)	English sudo rpm-ostree kargs --append='crashkernel=300M' Portuguese (Brazil) 50 characters edited sudo rpm-ostree kargs --append='crashkernel=256M' 3 years ago
rffontenelle Translation changed fedora-docs-l10n/fedora-coreos master/pages/debugging-kernel-crashes Portuguese (Brazil)	English sudo rpm-ostree kargs --append='crashkernel=300M' Portuguese (Brazil) 3 characters edited Current translation sudo rpm-ostree kargs --append='crashkernel=~~256~~300M' 3 years ago
None Suggestion added fedora-docs-l10n/fedora-coreos master/pages/debugging-kernel-crashes Portuguese (Brazil)	English sudo rpm-ostree kargs --append='crashkernel=300M' Portuguese (Brazil) 50 characters edited sudo rpm-ostree kargs --append='crashkernel=256M' 3 years ago
None Source string changed fedora-docs-l10n/fedora-coreos master/pages/debugging-kernel-crashes Portuguese (Brazil)	English 3 characters edited sudo rpm-ostree kargs --append='crashkernel=~~256~~300M' 3 years ago

Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English	Portuguese (Brazil)
No related strings found in the glossary.

7773837 String information

Source string description

type: delimited block -

Flags

no-wrap, placeholders:r"`[\w.\/\-_=@&*:$●+~()\] ]*`"

Source string location

pages/debugging-kernel-crashes.adoc:31

String age

3 years ago

Last updated

a year ago

Source string age

3 years ago

Translation file

po/pt_BR/master/pages/debugging-kernel-crashes.po, string 11

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.