Hi Philipp,
On Mon, Mar 28, 2022 at 01:59:40PM +0200, Philipp Rudo wrote:
Hi Coiby,
On Tue, 1 Mar 2022 17:40:00 +0800
Coiby Xu <coxu(a)redhat.com> wrote:
> Signed-off-by: Coiby Xu <coxu(a)redhat.com>
> ---
> kdumpctl.8 | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/kdumpctl.8 b/kdumpctl.8
> index 067117b..1a2ae8f 100644
> --- a/kdumpctl.8
> +++ b/kdumpctl.8
> @@ -50,6 +50,9 @@ Estimate a suitable crashkernel value for current machine. This is
a
> best-effort estimate. It will print a recommanded crashkernel value
while you are at it ;)
s/recommanded/recommended/
Thanks for catching the typo!
> based on current kdump setup, and list some details of memory usage.
> .TP
> +.I get-default-crashkernel
> +Return the default crashkernel value provided by kexec-tools.
How about:
Print the default crashkernel value used by kexec-tools. Useful when
setting the crashkernel value manually, e.g. via grubby.
Thanks for the suggestion! I'd like to suggest a small change. How
about:
Print the default crashkernel value used by kexec-tools. Useful as a
reference when setting the crashkernel value manually, e.g. via grubby.
Thanks
Philipp
> +.TP
> .I reset-crashkernel [--kernel=path_to_kernel] [--reboot]
> Reset crashkernel to default value recommended by kexec-tools. If no kernel
> is specified, will reset KDUMP_KERNELVER if it's defined in
/etc/sysconfig/kdump
--
Best regards,
Coiby