Comment 12 for bug 1415562

On 02/04/2015 01:29 PM, bugproxy wrote:
> ------- Comment From <email address hidden> 2015-02-04 19:20 EDT-------
> Louis & Chris, thanks for your help.
> The packages work as intended in both kdump & fadump modes.
> Couple of observations though:
>
> 1. When doing load/unload twice in succession, echo throws an error
>
> root@lop831:~# kdump-config load
> * fadump registered successfully
> root@lop831:~# kdump-config load
> /usr/sbin/kdump-config: line 301: echo: write error: Invalid argument
> * fadump registered successfully
> root@lop831:~#
> --
>
> root@lop831:~# kdump-config unload
> * fadump un-registered successfully
> root@lop831:~# kdump-config unload
> /usr/sbin/kdump-config: line 323: echo: write error: Invalid argument
> * fadump un-registered successfully
> root@lop831:~#
>

The code is where we set values into the sysfs directory:
echo 1 > $sys_fadump_registered

Where:
sys_fadump_registered=/sys/kernel/fadump_registered

Hari, can you confirm if kdump-config load/unload are actually changing
these values correctly? Perhaps the code needs to be adjusted.

> 2. While using network dump (SSH), would be nice if we can warn the user to run
> 'kdump-config propagate' before 'kdump-config load', if /root/.ssh/kdump_id_rsa is missing.
> This applies to both kdump & fadump modes
>
> Thanks
> Hari
>

Louis,
This might be a good general bug/issue to look into.

Thanks,
--chris