File: INSTALL

package info (click to toggle)
http-analyze 1.9e-2
  • links: PTS
  • area: non-free
  • in suites: hamm
  • size: 376 kB
  • ctags: 327
  • sloc: ansic: 3,493; sh: 185; makefile: 106
file content (96 lines) | stat: -rw-r--r-- 3,819 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
Here are some instructions how to install http-analyze 1.9e
-----------------------------------------------------------

To compile http-analyze, you will need the gd graphics library for fast
GIF creation written by Thomas Boutell.  You can download this software
from http://www.boutell.com/gd/. http-analyze has been tested with gd1.2.

http-analyze1.9e comes as a TAR archive with the following files:

	README		short description, copyright, license terms
	CHANGES		log of recent changes
	INSTALL		this file
	BUGS		known bugs
	Makefile	guess
	lint.out	output from lint
	cntrycode.c	code for handling top-level-domains
	cntrycode.h	definitions for cntrycode.c
	defs.h		common definitions
	http-analyze.c	the main program
	images.c	code generating GIF images
	utils.c		some utilities for http-analyze
	sample.conf	a sample configuration file
	rotate-httpd	a sample script for rotating logfiles
	http-analyze.man the manpage (nroff source)
	http-analyze.ps	a pre-formatted PostScript version of the manpage
	http-analyze.1	a pre-formatted ASCII version of the manpage


First, unpack the TAR file. This will create the directory http-analyze1.9e
with all required source files listed above. Edit the Makefile according to
your needs and generate the executable by issuing the command "make all".
Be sure to check the following macros:

	o The make macro LOCALBIN defines the directory where the executable
	  is installed and LOCALMAN defines the directory for the manpage.
	  The defaults are:
		LOCALBIN = /usr/local/bin
		LOCALMAN = /usr/local/man

	o The name of the gd library and the directory containing its include
	  files should be defined in the make macros GDLIB and GDINC.
	  The default values are:
		GDLIB = /usr/local/lib/libgd.a
		GDINC = /usr/local/include/gd

	o The following C defines (to be set in the make macro DEFINES) may
	  be used to adapt for different compilation environments:

	COUNT_EXTRA_BYTES	Account for the protocol overhead (if the
				http daemon does not do already)

	USER_AGENT		Include code for generating statistics
				about the user agents (requires logging
				of the user agent by the http daemon)

	USE_GETHOSTNAME		Use gethostname(2) to determine the
				server's full qualified domain name.
				If left undefined, http-analyze uses
				uname(2) to determine the nodename,
				which then may not be fully qualified.

	USE_FGETS		Use fgets(3) to read logfile entries
				rather than the built-in function which
				has been highly optimized for speed.

	BEST_IO_SIZE=#		You can define the recommended buffer
				size for optimum I/O when using the
				built-in function of http-analyze to
				process the logfile.  On my SGI Indy
				running IRIX 5.3, the best I/O size
				seems to be 64KB. This is the default
				if BEST_IO_SIZE is left undefined.

No further customization should be necessary at this point. If you must
modify http-analyze to get it compiled on your platform, please send me
the modifications so that I can integrate them into the sources for the
benefit of other people using the same platform.

Install the executable and the manpage with make "install". Optionally
install the rotate-httpd script to rotate your logfiles. Now you are
ready to go. For a first check, create a statistics for the current
month by running http-analyze as follows:
	http-analyze -vm /name/of/your/httpd/logfile

This will create a statistics summary in the current directory. (After
inspection, you can delete the files by issuing a "make clobber".)

If you want to define some default settings for http-analyze, create
a configuration file. See the file "sample.conf" and the manpage for
an example how to do this.

Now you can install a cron job which calls http-analyze on a regular
base. You also want to read the appropriate section in the manpage.

Have fun.