You could change your cron job to run Webalizer more often.  Or, you could 
run a tail -f against the important sites' logs, and keep an eye on the 
files being viewed. <G>

On 29 Jul 2002, Chris Mason wrote:

> Seems like I hit a sensitive topic - goodie...
> 
> I use webalizer on all sites, well, all the important ones. But when the
> server gets really busy, it doesn't help, I need to know what's being
> looked at now so I can go and look at the logs in real time.
> 
> We host all our own sites, so there's no financial interest, we get well
> paid for our hosting, but I want to see who's looking at what.
> Generally when we get a large load it's a crawl by a search engine.
> 
> Three of our sites account for most of our traffic, but how can you be
> sure, so I want a way to check. I am bigh on monitoring, using
> netsaint/nagios, cricket, iptraf and a web based service to ensure
> reliabilty and trace problems.
> 
> I know as soon as the server gets loaded up, but I don't know what site
> is causing it.
> 
> I'll try the MRTG ans see hwo that works out, thanks for the
> suggesitons,
> 
> Chris
> 
> On Mon, 2002-07-29 at 19:43, Emmanuel Seyman wrote:
> > On Mon, Jul 29, 2002 at 04:10:25PM -0700, daniel wrote:
> > >
> > > i've never used it, but doesn't webalizer do the job?  it should chart
> > > everything out for you as well.
> > 
> > Webalizer cannot tell the difference between virtual hosts.
> > You could setup a webalizer instance for every vhost and compare
> > the reports but it isn't very practical.
> > 
> > Emmanuel
> > 
> > 
> > 
> > _______________________________________________
> > Redhat-list mailing list
> > [EMAIL PROTECTED]
> > https://listman.redhat.com/mailman/listinfo/redhat-list
> 
> 
> 
> 
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
> 



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to