From: Ryan O'Hara <rohara@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] SCSI-PR watchdog script
Date: Tue, 1 Mar 2011 10:22:54 -0600 [thread overview]
Message-ID: <20110301162254.GA341@redhat.com> (raw)
Attached is a new watchdog script to be used in conjunction with the
fence_scsi agent. Note that this script requires the previous two
patches I posted for fence_scsi. Specifically, this script depends on
the existence of the fence_scsi.key and fence_scsi.dev files located
in /var/run/cluster directory.
This script gets the local node's key from the fence_scsi.key file and
a list of devices from the fence_scsi.dev file. Each of these files is
created when unfencing occurs. The watchdog script then periodically
checks that the key is registered with at least one of the
devices. Note that the script will only trigger reboot via watchdog
(exit 2) if the key is not registered with any of the devices.
Ryan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: check_scsi.pl
Type: application/x-perl
Size: 2850 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20110301/e1b4c1dc/attachment.pl>
reply other threads:[~2011-03-01 16:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110301162254.GA341@redhat.com \
--to=rohara@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).