All of lore.kernel.org
 help / color / mirror / Atom feed
From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] New wdmd policy for refpolicy contrib.
Date: Fri, 02 Dec 2011 08:34:01 -0500	[thread overview]
Message-ID: <4ED8D3C9.2030202@redhat.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Man wdmd


WDMD(8)

NAME
       wdmd - watchdog multiplexing daemon

SYNOPSIS
       wdmd [OPTIONS]

DESCRIPTION
       This daemon opens /dev/watchdog and allows multiple independent
sources
       to detmermine whether each KEEPALIVE is done.  Every test
interval  (10
       seconds),  the  daemon  tests  each  source.   If  any  test
fails, the
       KEEPALIVE is not done.  In a standard configuration, the
watchdog timer
       will  reset  the  system  if no KEEPALIVE is done for 60
seconds ("fire
       timeout").  This means that if single test fails 5-6 times in
row,  the
       watchdog  will  fire and reset the system.  With multiple test
sources,
       fewer separate failures back to back can also cause a reset, e.g.
...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7Y08kACgkQrlYvE4MpobMpQACfYB/kPHEkkv4M1H0qG6BVUA4w
9IcAoIsWBkkEzyhSj5hr+wg92MuSC2Xn
=gcph
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: wdmd.patch
Url: http://oss.tresys.com/pipermail/refpolicy/attachments/20111202/8ac9f94a/attachment.pl 

             reply	other threads:[~2011-12-02 13:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02 13:34 Daniel J Walsh [this message]
2012-01-05 18:30 ` [refpolicy] New wdmd policy for refpolicy contrib Sven Vermeulen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4ED8D3C9.2030202@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=refpolicy@oss.tresys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.