-rw-r--r--

README

27

< Edward Rudd olspan='4'>@@ -1,4 +1,4 @@ 1$Id: README,v 1.2 2001/12/03 19:54:02 helios Exp $ 1$Id: README,v 1.3 2001/12/07 03:52:56 helios Exp $ 2 2 3 3 4Homepage 4Homepage@@ -105,10 +105,6 @@ request_uri: corresponds to the Apache %U directive. Contains the 105 needed for log analysis, and saves the database a LOT of wasted growth 105 needed for log analysis, and saves the database a LOT of wasted growth 106 on unneeded bytes. 106 on unneeded bytes. 107 107 108request_duration: corresponds to the Apache %T directive. Contains the 109 time in seconds that it took to serve the request. 110 Example: 2 111 112virtual_host: contains the VirtualHost that is making the log entry. This 108virtual_host: contains the VirtualHost that is making the log entry. This 113 allows you to log multiple VirtualHosts to a single MySQL database and 109 allows you to log multiple VirtualHosts to a single MySQL database and 114 yet still be able to extract them for separate analysis. 110 yet still be able to extract them for separate analysis.@@ -149,7 +145,7 @@ Notes 149* The 'time_stamp' field is stored in an UNSIGNED INTEGER column, in the 145* The 'time_stamp' field is stored in an UNSIGNED INTEGER column, in the 150 standard unix "seconds since 1/1/1970 12:00:00" format. This is 146 standard unix "seconds since 1/1/1970 12:00:00" format. This is 151 superior to storing the access time as a string due to size 147 superior to storing the access time as a string due to size 152 requirements: an UNSIGNED INT type fits in 4 bytes. The Apache date 148 requirements: an UNSIGNED INT type fits in 4 bytes, whereas the Apache date 153 string (e.g. "18/Nov/2001:13:59:52 -0800") requires 26 bytes -- 149 string (e.g. "18/Nov/2001:13:59:52 -0800") requires 26 bytes -- 154 significantly larger, and those extra 22 bytes will add up over the 150 significantly larger, and those extra 22 bytes will add up over the 155 thousands of accesses that a busy server will experience. Besides, 151 thousands of accesses that a busy server will experience. Besides,@@ -187,19 +183,6 @@ Notes 187 makes perfect sense anyway. 183 makes perfect sense anyway. 188 184 189 185 190Disclaimer 191---------- 192 193It works for me (I've tested it on my '2 hits/busy day' home Linux box, 194and afterwards on our pretty busy tucows mirror (>100K hits a day) and 195it appears to be working fine. 196 197If it doesn't, and causes you damage of any sort, including but not 198limited to losing logs, losing money or your girlfriend leaving you 199(read 'boyfriend' where applicable), I'm not liable to anything. Bug 200reports and constructive flame mail are ok, though (both about the code 201and this quickly-written README file). 202 203 186 204Author / Maintainer 187Author / Maintainer 205------------------- 188-------------------@@ -207,11 +190,11 @@ Author / Maintainer 207The actual logging code was taken from the already existing flat file 190The actual logging code was taken from the already existing flat file 208text modules, so all that credit goes to the Apache Server group. 191text modules, so all that credit goes to the Apache Server group. 209 192 210The MySQL routines and directives was added in by Zeev Suraski 193The MySQL routines and directives were added by Zeev Suraski 211<bourbon@netvision.net.il> 194<bourbon@netvision.net.il>. 212 195 213Changes from 1.06 on and the new documentation were added by 196Changes from 1.06 on and the new documentation were added by 214Chris Powell <chris@grubbybaby.com>. It seems that the module had fallen 197Chris Powell <chris@grubbybaby.com>. It seems that the module had fallen 215into the "unmaintained" category -- it hadn't been updated since 1998 -- 198into the "unmaintained" category -- it hadn't been updated since 1998 -- 216so I've adopted it as the new maintainer. 199so Chris adopted it as the new maintainer. 217 200