--Compiling squidview

  $ ./configure
  $ make

The program is c/c++ and uses the ncurses library for obtaining
some keystrokes. Old gcc compilers can fail compiling this
program; if so start afresh and:

  $ cp Makefile.old Makefile
  $ make oldgcc

... and install manually.

If you are compiling on Solaris I have heard of one instance where
it is necessary to link against Solaris' own curses library. To do
this you need to link against lcurses rather than lncurses.

--Installation

If "configure" and "make" are successful:

  # make install
  
Or if you aren't the superuser the program will still run if
you have read access to the squid log file.

This program assumes the main squid log file is here:
  /usr/local/squid/var/logs/access.log
If it isn't just symlink it appropriately from the following
default. This directory and links are made in the user's home
space when first run by the user.

  graeme@localhost:~/.squidview$ ls -l
  HOWTO -> /usr/local/share/doc/squidview/HOWTO
  log1 -> /usr/local/squid/var/logs/access.log
  log2 -> log1
  log3 -> log1
  users
  words

In this case squidview expects the primary log to be "log1",
and the symlink redirects it to where the file actually is.
The same thing applies to the readme.

This tar.gz archive comes with an example access.log named
example.log. Symlink it to view it with squidview.

"users" and "words" are reporting files - these can be symlinks
to /etc if you would rather have these files there. "aliases" is
another text file, this time for mapping IP numbers to user-
defined names.

This package comes with example "users", "words" and "aliases"
files you can build on.