From d7f381254270028c7d239463521005f576575151 Mon Sep 17 00:00:00 2001 From: "jake%acutex.net" <> Date: Sat, 19 Jan 2002 07:26:39 +0000 Subject: Latest version of compiled docs (picking up recent SGML changes). --- docs/html/postinstall-check.html | 66 ++++++++++++++++++++-------------------- 1 file changed, 33 insertions(+), 33 deletions(-) (limited to 'docs/html/postinstall-check.html') diff --git a/docs/html/postinstall-check.html b/docs/html/postinstall-check.html index 5b0cbbb7a..6857326ab 100644 --- a/docs/html/postinstall-check.html +++ b/docs/html/postinstall-check.html @@ -19,7 +19,7 @@ REL="NEXT" TITLE="User Administration" HREF="useradmin.html">
After installation, follow the checklist below to help ensure +> After installation, follow the checklist below to help ensure that you have a successful installation. If you do not see a recommended setting for a parameter, consider leaving it at the default while you perform your initial tests on your Bugzilla setup.
Bring up
Bring up editparams.cgi in your web
browser. This should be available as the Set
Set "maintainer" to For example, if your bugzilla query page is
+>
For example, if your bugzilla query page is
http://www.foo.com/bugzilla/query.cgi, set your
Set "usebuggroups" to "on"
Set "usebuggroups" to "on" only if you
may wish to restrict access to products. I suggest leaving
@@ -160,7 +160,7 @@ CLASS="QUOTE"
>
"usebuggroupsentry", when set to @@ -172,7 +172,7 @@ CLASS="QUOTE" installations where product isolation is a necessity.
Set "usebuggroupsentry" to "on" if you absolutely need to +> Set "usebuggroupsentry" to "on" if you absolutely need to restrict access to bugs from the moment they are submitted through resolution. Once again, if you are simply testing your installation, I suggest against turning this parameter @@ -182,7 +182,7 @@ CLASS="QUOTE" >
You run into an interesting problem when Bugzilla reaches a +> You run into an interesting problem when Bugzilla reaches a high level of continuous activity. MySQL supports only table-level write locking. What this means is that if someone needs to make a change to a bug, they will lock the @@ -200,16 +200,16 @@ CLASS="QUOTE" extremely high-traffic Bugzilla databases.
Set "shadowdb" to "bug_shadowdb" if you will be running a +> Set "shadowdb" to "bug_shadowdb" if you will be running a *very* large installation of Bugzilla. The shadow database enables many simultaneous users to read and write to the database without interfering with one another.