On Sat, Jun 16, 2001 at 12:51:58PM -0400, Ashley T . Howes wrote:

I just looked at these. In June 2001 3.3% of visitors were using a BBC Micro

That is interesting. I wonder what kind of web browser you could write to run in a machine with 32K RAM. Of course, if you made the browser a "language ROM" you get an additional 16K for your code, and can use the RAM that frees up for data.

So, does anyone know of a web browser for the BBC Micro?

The other possibility, of course, is that someone has a browser that lets the user configure the agent header (doesn't opera let you do that?), or a proxy server that can be made to falsify it.

The other interesting thing is that this is a Linux related web site and most of the browsers appear to be MS IE on Windows!

Steve.

On Mon, 18 Jun 2001 10:57:42 +0100 (BST), Paul Tansom wrote:

Cool, another Webalizer user - I like that package, very easy to setup and use :-) How have you automated it? Cron, or dropped it into the logrotate?

It's an automated script which combines the whole of Zeus' web logs for the month into one file and then spits out the data into Webalizer. Zeus automatically creates a new log file per day (which I wish it didn't - I'd really like the option of having weekly or monthly automated log rotation) and thus a script is required to combine everything together.

The script also fires off stats for other web sites that are hosted on the box, so it's pretty darn convient. I remember using Webalizer several years ago when I was working for an ISP in Norwich, and then it's popped it's head up and has been used in every other job I've been to - at Ision Internet I used it to keep tabs on the general stats for the free NDO service. It was very useful as we could see who had the very dodgy sites (porn or warez) hosted on the servers as we could simply look at how much data had been transferred per site :) Upon visiting the site it usually contained something dodgy enough to contrevene the terms and conditions of the service and I'd pull their account (BOFH mode) :)

Where I am now, we simply use it for providing stats for customer's web sites. A script simply runs a bunch of webalizer configuration files (one for each site) through webalizer and there you've got instant stats. A simply bash script simply creates the configuration file for each new client that wants stats added to their site, as well as generating the relavent .htaccess/.htpasswd files. An ultra-low cost (i.e. free) solution to the likes of Webtrends and other commercial log analyzers out there.

BTW, if DNS hasn't propergated yet (which it definately should have by now, but you never know!), you can also view the stats from http://www.alug.org.uk/usage or http://www.anglian.lug.org.uk/usage.

Regards,

Martyn