The primary configuration file for Urchin is in your ~/usr/local/urchin/ directory and is named config. The format
of the config file is similar to your apache httpd.conf file, and contains instructions on what the listed directives
mean. You can use the urchin configuration file to set up automatic logfile rotation, DNS resolution , and reporting styles. The file
also contains important license information.
NOTE: Do not edit the license information in your urchin configuration file. If the license information is
changed, it can cause the program to stop functioning
|
The LogDestiny directive is used to determine whether Urchin should archive, delete, or leave logfiles alone.
The second section of the urchin configuration file contains the individual report settings. There must be a Report configured for
each domain you want Urchin reporting done. The default install sets up a report for each of the hosts listed in your
httpd.conf file, and configures the reports to be stored in the urchin directory off the host's DocumentRoot
directory.
The following is an example of what a Report configuration should look like:
<Report>
ReportName: YOUR-DOMAIN.NAME
ReportDirectory: /usr/local/LOGIN/usr/local/etc/httpd/vhosts/YOUR-DOMAIN.NAME/htdocs/urchin/
TransferLog: /usr/local/LOGIN/usr/local/etc/httpd/vhosts/YOUR-DOMAIN.NAME/logs/access_log
ErrorLog: /usr/local/LOGIN/usr/local/etc/httpd/vhosts/YOUR-DOMAIN.NAME/logs/error_log
</Report>
NOTE: Each directive should be on a single line in the config file.
|
NOTE: Urchin requires CGI execution to be enabled in the report directory. If you don't want your subhosts to
be able to run their own CGIs, you may want to locate their report directory outside their Document Root so they can not
add scripts to that directory
|