On Sat, Dec 01, 2001 at 11:49:23PM -0800, Bill Moseley wrote:
Any suggestions for favorite ones? wusage seems to require a lot of
resources -- maybe that's not unusual? It runs once a week. Here's a
about six days worth of requests. Doesn't see like that many.
I roll my own. It depends
On Sat, 1 Dec 2001, Bill Moseley wrote:
Any suggestions for favorite ones? wusage seems to require a lot of
resources -- maybe that's not unusual? It runs once a week. Here's a
about six days worth of requests. Doesn't see like that many.
%wc -l access_log
1185619 access_log
PID
Bill Moseley [EMAIL PROTECTED] writes:
Any suggestions for favorite ones? wusage seems to require a lot of
resources -- maybe that's not unusual? It runs once a week. Here's a
about six days worth of requests. Doesn't see like that many.
analog - but _do_ read the words that go with it,
On Sun, Dec 02, 2001 at 12:52:11PM +, Dave Hodgkinson wrote:
Bill Moseley [EMAIL PROTECTED] writes:
Any suggestions for favorite ones? wusage seems to require a lot of
resources -- maybe that's not unusual? It runs once a week. Here's a
about six days worth of requests. Doesn't see
At 10:09 AM 12/2/2001 +, Matt Sergeant wrote:
PID USERNAME THR PRI NICE SIZE RES STATE TIMECPU COMMAND
17223 operator 1 442 747M 745M cpu14 19.2H 45.24% wusage
Ouch. Try analog.
PID USERNAME THR PRI NICE SIZE RES STATE TIMECPU COMMAND
17223 operator 1
On Dec 02, 2001 at 07:33:55 -0800, Bill Moseley wrote:
Date: Sun, 02 Dec 2001 07:33:55 -0800
To: [EMAIL PROTECTED]
From: Bill Moseley [EMAIL PROTECTED]
Subject: Re: [OT] log analyzing programs
At 10:09 AM 12/2/2001 +, Matt Sergeant wrote:
PID USERNAME THR PRI NICE SIZE RES
Any suggestions for favorite ones? wusage seems to require a lot of
resources -- maybe that's not unusual? It runs once a week. Here's a
about six days worth of requests. Doesn't see like that many.
%wc -l access_log
1185619 access_log
PID USERNAME THR PRI NICE SIZE RES STATE TIME
