From: Jason Molenda <jason-swarelist@molenda.com>
To: Matthew Galgoci <mgalgoci@redhat.com>
Cc: overseers@sources.redhat.com, fche@redhat.com
Subject: Re: system woes likely due to hardware/fs problems
Date: Tue, 06 Apr 2004 22:53:00 -0000 [thread overview]
Message-ID: <20040406155324.A80600@molenda.com> (raw)
In-Reply-To: <20040406154757.A74795@molenda.com>; from jason-swarelist@molenda.com on Tue, Apr 06, 2004 at 03:47:57PM -0700
On Tue, Apr 06, 2004 at 03:47:57PM -0700, Jason Molenda wrote:
> For what it's worth, /var/log/monitors has a periodic sampling of
> a few different measures. It's been well over a year since I've
> looked at it so maybe it's completely broken, but my guess is that
> it's still pretty much working.
BTW I should note that most of the scripts do stuff like give the
ps entries for all running cvs processes. So it's most useful like
cd /var/log/montiors
cd all-cvs
wc -l */*
and you get a list like
2 2004-04-05/03:15
2 2004-04-05/03:30
8 2004-04-05/03:45
18 2004-04-05/04:00
19 2004-04-05/04:15
19 2004-04-05/04:30
20 2004-04-05/04:45
6 2004-04-05/05:00
8 2004-04-05/05:15
5 2004-04-05/05:30
6 2004-04-05/05:45
8 2004-04-05/06:00
16 2004-04-05/06:15
16 2004-04-05/06:30
15 2004-04-05/06:45
10 2004-04-05/07:00
10 2004-04-05/07:15
13 2004-04-05/07:30
16 2004-04-05/07:45
12 2004-04-05/08:00
etc. This particular one seems to be including cvsupd in its
output, so it's always off by one. But you get the idea.
next prev parent reply other threads:[~2004-04-06 22:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 21:04 Angela Marie Thomas
2004-04-06 21:14 ` Frank Ch. Eigler
2004-04-06 21:15 ` Ian Lance Taylor
2004-04-06 21:36 ` Angela Marie Thomas
2004-04-06 22:39 ` Matthew Galgoci
2004-04-06 22:48 ` Jason Molenda
2004-04-06 22:53 ` Jason Molenda [this message]
2004-04-06 23:32 ` Angela Marie Thomas
2004-04-06 23:59 ` Jason Molenda
2004-04-07 0:06 ` Ian Lance Taylor
2004-04-08 21:19 ` Gerald Pfeifer
2004-04-07 2:55 ` Christopher Faylor
2004-04-07 2:49 ` Christopher Faylor
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=20040406155324.A80600@molenda.com \
--to=jason-swarelist@molenda.com \
--cc=fche@redhat.com \
--cc=mgalgoci@redhat.com \
--cc=overseers@sources.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 read-only IMAP folder(s) and NNTP newsgroup(s).