From: Ben Woodard <woodard@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: Re: new utility for decoding salinfo records
Date: Tue, 11 Jan 2005 21:12:37 +0000 [thread overview]
Message-ID: <1105477957.22104.170.camel@quince.llnl.gov> (raw)
In-Reply-To: <1105458388.22104.7.camel@quince.llnl.gov>
On Tue, 2005-01-11 at 11:03, David Mosberger wrote:
> >>>>> On Tue, 11 Jan 2005 07:46:28 -0800, Ben Woodard <woodard@redhat.com> said:
>
> Ben> salinfo_decode2 also has the capability to generate
> Ben> output that is designed to be easily parsed by a machine. This
> Ben> is useful when you want to automate monitoring of large numbers
> Ben> of machines. For example, instead of having scripts notify you
> Ben> every time an ignorable single bit memory error occurs, the
> Ben> monitoring scripts can easily ignore those errors and only
> Ben> point out higher priority error conditions.
>
> It seems a bit dangerous to me to encourage ignoring single-bit
> errors. Perhaps it would be better to suggest to summarize these
> errors?
>
> --david
Does this sound like better wording to you?
salinfo_decode2 also has the capability to generate output that is
designed to be easily parsed by a machine. This is useful when you want
to automate monitoring of large numbers of machines. For example,
instead of having scripts notify the sysadmin every time an isolated
single bit memory error occurs, the monitoring scripts can be designed
to ignore those isolated errors (but save them for later summary
reporting) and notify the sysadmin only if the rate exceeds a specified
threshold.
-ben
next prev parent reply other threads:[~2005-01-11 21:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 15:46 new utility for decoding salinfo records Ben Woodard
2005-01-11 19:03 ` David Mosberger
2005-01-11 19:49 ` Luck, Tony
2005-01-11 20:25 ` David Mosberger
2005-01-11 20:26 ` Ben Woodard
2005-01-11 20:53 ` Mark Goodwin
2005-01-11 21:03 ` Ben Woodard
2005-01-11 21:12 ` Ben Woodard [this message]
2005-01-11 21:22 ` Russ Anderson
2005-01-11 21:23 ` Luck, Tony
2005-01-11 21:25 ` David Mosberger
2005-01-11 21:36 ` David Mosberger
2005-01-11 21:36 ` Matthias Fouquet-Lapar
2005-01-11 21:37 ` Ben Woodard
2005-01-11 21:42 ` David Mosberger
2005-01-11 21:58 ` Russ Anderson
2005-01-11 22:02 ` David Mosberger
2005-01-11 22:26 ` Matthias Fouquet-Lapar
2005-01-12 4:10 ` Keith Owens
2005-01-12 6:08 ` Luck, Tony
2005-01-12 6:43 ` Keith Owens
2005-01-12 9:34 ` Matthias Fouquet-Lapar
2005-01-12 16:57 ` Ben Woodard
2005-01-12 20:46 ` Keith Owens
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=1105477957.22104.170.camel@quince.llnl.gov \
--to=woodard@redhat.com \
--cc=linux-ia64@vger.kernel.org \
/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