On 08-Jul-2016 6:51 am, "Dave Young" <dyoung(a)redhat.com> wrote:
On 07/06/16 at 06:40pm, Pratyush Anand wrote:
> On Wed, Jul 6, 2016 at 7:29 AM, Dave Young <dyoung(a)redhat.com> wrote:
> > 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.
> >> .B kdumpctl
> >> provides more details for debug and a helper to setup ssh key
> >> +.SH NOTES
> >> +If a watchdog has been activated manually or by any daemon after
> >> +service start, then user must restart kdump service in
> >> +kdump initrd with active watchdog module.
> >> +If a custom application and not systemd daemon is used to activate
> >> +watchdog then, it is user's responsibility to pass
name of the
> >> +in /etc/kdump.conf:extra_bins and the watchdog kick
> >> +/etc/kdump.conf:kdump_pre.
> > Maybe this is not necessary to be covered in kdumpctl manpage.
> > we only support systemd wdt interface somewhere should be
> I remember vaguely that I had got comment for RFC patch to include
> these information in man page.
> Yes, if we limit to systemd support only then it will be easier. But
> where to put that information other than man page.
Maybe add one section in the howto.txt about the wdt notes should be fine.
Ok, will do in v2.
> > Systemd wdt will always run before kdump service?
> >> +
> >> .SH COMMANDS
> >> .TP
> >> .I start
> >> --
> >> 2.5.5
> >> _______________________________________________
> >> kexec mailing list
> >> kexec(a)lists.fedoraproject.org