John Berninger 04e1870
Bugzilla is a powerful bug tracking system used by a large number of open
John Berninger 04e1870
source projects.  
John Berninger 04e1870
John Berninger 04e1870
In order to use Bugzilla, you will first need to configure it for your 
John Berninger 04e1870
environment.  The first step to doing this is to run the checksetup.pl
John Berninger 04e1870
script, which will perform module version checks and create an initial
John Berninger 04e1870
config file in /etc/bugzilla called localconfig.  You then need to ensure
John Berninger 04e1870
the values in this file are accurate for your environment.
John Berninger 04e1870
John Berninger 04e1870
Once this is done, you may need to modify default settings for your database
John Berninger 04e1870
to ensure it accepts Bugzilla data properly.  Please see 
Emmanuel Seyman 2adbb85
http://www.bugzilla.org/docs/4.0/en/html/configuration.html for specifics of 
John Berninger 04e1870
database setting modifications.
John Berninger 04e1870
John Berninger 04e1870
Lastly, simply re-run checksetup.pl to populate the database tables, set up
John Berninger 04e1870
the templates, and add the administrator ID.  You should be done at this point.
John Berninger 882b4d1
John Berninger 882b4d1
There are two useful cron jobs which are included with Bugzilla which should be
John Berninger 882b4d1
put in place after configuration is done.  The first is a daily cron job for 
John Berninger 882b4d1
statistics collection.  This is in the file "cron.daily" and can be enabled by
John Berninger 882b4d1
simply copying this file to /etc/cron.daily/bugzilla (or any other file name
John Berninger 882b4d1
in the /etc/cron.daily/ directory).  The second is the "whine" cron job,
Emmanuel Seyman 439e2d3
designed to run every 15 minutes.  To enable this job, simply copy the
John Berninger 882b4d1
cron.whine file to /etc/cron.d/bugzilla (or any othe filename within the
John Berninger 882b4d1
/etc/cron.d/ directory).