phosphor-watchdog: Continue after performing action

In the past, expiry of the phosphor-watchdog meant that some type of
reset action was peformed on the machine and the phosphor-watchdog would
be restarted during the reset process. Now that we support multiple
actions and allow the timer to expire for the NONE action, this
assumption is no longer true. If a NONE watchdog expires the daemon will
die and the watchdog will no longer be armable. Fix this using the
continue option of the phosphor-watchdog to continue servicing watchdog
requests after expiry.

Change-Id: I8428087e7c98d49ebd80bbc7b7d5f4225dff7ffd
Signed-off-by: William A. Kennington III <wak@google.com>
1 file changed
tree: d1f161dba244b9ae0297cf135d0c09539c9d8c53
  1. classes/
  2. common/
  3. conf/
  4. COPYING.apache-2.0
  5. COPYING.MIT
  6. LICENSE
  7. README.md
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.