A typical example is a web server log which maintains a history of page requests. The W3C maintains a standard format (the Common Log Format) for web server log files, but other proprietary formats exist. More recent entries are typically appended to the end of the file. Information about the request, including client IP address, request date/time, page requested, HTTP code, bytes served, user agent, and referrer are typically added. These data can be combined into a single file, or separated into distinct logs, such as an access log, error log, or referrer log. However, server logs typically do not collect user-specific information.
These files are usually not accessible to general Internet users, only to the webmaster or other administrative person. A statistical analysis of the server log may be used to examine traffic patterns by time of day, day of week, referrer, or user agent. Efficient web site administration, adequate hosting resources and the fine tuning of sales efforts can be aided by analysis of the web server logs. Marketing departments of any organization that owns a website should be trained to understand these powerful tools.
We've configured cheshire to record most Apache httpd and PHP errors in the web server error log file.
Run the tail utility with the -f option (it stands for 'follow') to see all new data as it's appended in realtime to cheshire's Apache www-student virtual host's error log file:
% tail -f /var/log/httpd/httpd-error_log
... or similarly, view successful HTTP data access requests:
% tail -f /var/log/httpd/httpd-access_log