Re: [OT] log analyzing programs

2001-12-02 Thread Brian Reichert

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 the analysis I need to perform.  I
tend to scan them, and chuck the the elements into a MySQL database,
so I can run real checks.

 Bill Moseley
 mailto:[EMAIL PROTECTED]

-- 
Brian 'you Bastard' Reichert[EMAIL PROTECTED]
37 Crystal Ave. #303Daytime number: (603) 434-6842
Derry NH 03038-1713 USA Intel architecture: the left-hand path



Re: [OT] log analyzing programs

2001-12-02 Thread Matt Sergeant

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 USERNAME THR PRI NICE  SIZE   RES STATE   TIMECPU COMMAND
 17223 operator   1  442  747M  745M cpu14  19.2H 45.24% wusage

Ouch. Try analog.

-- 
Matt/

/||** Founder and CTO  **  **   http://axkit.com/ **
   //||**  AxKit.com Ltd   **  ** XML Application Serving **
  // ||** http://axkit.org **  ** XSLT, XPathScript, XSP  **
 // \\| // ** mod_perl news and resources: http://take23.org  **
 \\//
 //\\
//  \\




Re: [OT] log analyzing programs

2001-12-02 Thread Dave Hodgkinson

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, know what you're
analysing. i have a stats redux note on my site too.

-- 
David Hodgkinson, Wizard for Hirehttp://www.davehodgkinson.com
Editor-in-chief, The Highway Star   http://www.deep-purple.com
Deep Purple Family Tree news  http://www.slashrock.com
   Interim Technical Director, Web Architecture Consultant for hire



Re: [OT] log analyzing programs

2001-12-02 Thread Matthew Byng-Maddick

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 like that many.
 analog - but _do_ read the words that go with it, know what you're
 analysing. i have a stats redux note on my site too.

We like analog, Stephen Turner is a Cam.pm member, and makes regular
appearances at our social meets. I've looked at webalizer too, but webalizer
is appallingly written, keeps everything in globals (though I believe analog
also currently does this and Stephen said he'd like to change it), and uses
scary amounts of memory. It also doesn't have particularly good integrity
checking for its database dumps.

MBM

-- 
Matthew Byng-Maddick [EMAIL PROTECTED]   http://colondot.net/



Re: [OT] log analyzing programs

2001-12-02 Thread Bill Moseley

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   02  747M  745M cpu14  27.1H 47.57% wusage

Well at least after another 8 hours of CPU it's not leaking ;)



Bill Moseley
mailto:[EMAIL PROTECTED]



Re: [OT] log analyzing programs

2001-12-02 Thread Rick Myers

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 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   02  747M  745M cpu14  27.1H 47.57% wusage
 
 Well at least after another 8 hours of CPU it's not leaking ;)

I don't have a running analog right this second, but I run
it on the following daily. I sure don't see the cpu usage
you see, but it does take a couple hours to finish. (Mostly
because analog doesn't hammer the dns server.)

-rw-r--r--   1 root root 311413188 Dec  2 10:50 access_log
-rw-r--r--   1 root root 89773421 Dec  2 10:37 azaleas2_access_log
-rw-r--r--   1 root root 13499455 Dec  2 10:21 azaleas3_access_log
-rw-r--r--   1 root root 10692999 Dec  2 10:37 error_log
-rw-r--r--   1 root root  7786067 Dec  2 00:33 sumthin2_log
-rw-r--r--   1 root root   142857 Nov  2 02:44 sumthin3_log

--rick