NutmegCT said:
Thanks Dave! 18 in the poll, so I'm taking it as a good approximation of Pub posters.
I think most webservers these days actually record the browser and o/s of each connection. Basil would likely have a more detailed "warez" count already logged on his BCF server.
Tom
DrEntropy said:
Yup.
Yup, I know Apache on Linux does log user agent data. That normally includes OS and browser. The only catch to that is some web browser will "lie" about their browser type, typically to get around people that want to build sites strictly for IE. Since building sites in that manner isn't common place anymore (not saying it doesn't still happen), it shouldn't be much of a factor.
I haven't bother poking around and trying to figure out what this server is running (as it can often appear to be malicious in nature). However, if it's Linux/*nix w/ Apache, something like the following might help gather more accurate statistics:
(run in the directory with your access_log files)
awk '{print $12" "$13}' <access log file name here> | sort | uniq -c | sort -nr | head -20
Depending on the layout of your access_log files, $12 and $13 might need to change slightly. In a space delimited file $12 is the browser version, and $13 is the OS. Though, because this command uses space delimiting to separate out data from the log file, the OS information will not be 100% accurate. From checking my logs, it'd result in "Windows" instead of "Windows NT 5.1" (WindowsXP).
Most servers at least offer free web traffic statistics. The servers I work w/ daily offer a choice between AWStats and Webilizer which parse the web traffic logs on the server. Other web analytics that I know about are Urchin (server side processing of statistics) and Google Anaylitics. Google Analytics is free. Though, it requires you to add code to your sites for it to work, normally to call a JavaScript file to allow Google to record the page hit. If Google Analytics is used, then it's advisable to add their snippet of code for their .js file to the "footer" file for the site. This makes it quick and easy; edit 1 file and get records of every page load. Also, w/ the call to the js file in the footer, it won't impede site speed much because the js script will be loading after everything else has displayed.