lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <12D0F3A5-602E-4C4B-908D-55C3C50823BB@fb.com>
Date:   Tue, 27 Nov 2018 06:11:46 +0000
From:   Tao Ren <taoren@...com>
To:     "Jerry.Hoemann@....com" <jerry.hoemann@....com>
CC:     Guenter Roeck <linux@...ck-us.net>,
        Wim Van Sebroeck <wim@...ux-watchdog.org>,
        "linux-watchdog@...r.kernel.org" <linux-watchdog@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "openbmc@...ts.ozlabs.org" <openbmc@...ts.ozlabs.org>
Subject: Re: [PATCH] watchdog: core: suppress "watchdog did not stop" message

On 11/26/18, 5:31 PM, "Jerry Hoemann" <jerry.hoemann@....com> wrote:
> Tao,
> 
> If you're on a system running systemd, the default behavior is to
> enable the watchdog during shutdown.  This guards against shutdown hanging.
> So this message will be routinely printed out during orderly shutdown.

Thank you Jerry for the comments.

I actually use a separate daemon process to kick the watchdog on my BMC system. The daemon monitors temperature sensors and other system states and kicks watchdog periodically: if the daemon gets stuck or exits, then the machine needs to reboot even if kernel/systemd is fine. Perhaps I need to look for a better/official way to manage the watchdog device..

BTW, I will be travelling abroad in the new few days and may not be able to reply emails timely. Thank you again for jumping in.

Best regards,
Tao Ren
    

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ