On 07/05/16 at 11:41am, Pratyush Anand wrote:
Add notes in kdumpctl man page with limitations of kdump when used
in
conjunction with watchdog.
Signed-off-by: Pratyush Anand <panand(a)redhat.com>
---
kdumpctl.8 | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/kdumpctl.8 b/kdumpctl.8
index b446b81bc37a..713342700b17 100644
--- a/kdumpctl.8
+++ b/kdumpctl.8
@@ -16,6 +16,15 @@ to start / stop / enable kdump service instead. However,
.B kdumpctl
provides more details for debug and a helper to setup ssh key authentication.
+.SH NOTES
+If a watchdog has been activated manually or by any daemon after kdump
+service start, then user must restart kdump service in order to rebuild
+kdump initrd with active watchdog module.
+If a custom application and not systemd daemon is used to activate and kick
+watchdog then, it is user's responsibility to pass name of the application
+in /etc/kdump.conf:extra_bins and the watchdog kick command in
+/etc/kdump.conf:kdump_pre.
Maybe this is not necessary to be covered in kdumpctl manpage. Declare that
we only support systemd wdt interface somewhere should be enough.
Systemd wdt will always run before kdump service?
+
.SH COMMANDS
.TP
.I start
--
2.5.5
_______________________________________________
kexec mailing list
kexec(a)lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/kexec@lists.fedoraproject.org
Thanks
Dave