From c88af85fd2d0627287386f8ed21ad3baa7e93fdc Mon Sep 17 00:00:00 2001
From: "jake%bugzilla.org" <>
Date: Tue, 7 Dec 2004 19:41:59 +0000
Subject: Bug 271360 - Moving the Troubleshooting section into an appendix
instead. Also, moved a few items out of the FAQ and into this new appendix.
---
docs/xml/faq.xml | 130 +++----------------------------------------------------
1 file changed, 7 insertions(+), 123 deletions(-)
(limited to 'docs/xml/faq.xml')
diff --git a/docs/xml/faq.xml b/docs/xml/faq.xml
index 59cb330d9..fbab94212 100644
--- a/docs/xml/faq.xml
+++ b/docs/xml/faq.xml
@@ -584,129 +584,6 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl
-
-
-
- Why do users have to log in every time they access a page? This
- affects everyone who accesses my Bugzilla. (If this only affects
- some of your users, see the next FAQ item.)
-
-
-
-
- The most-likely cause is that the "cookiepath" parameter is not set
- correctly in the Bugzilla configuration. You can change this (if
- you're a Bugzilla administrator) from the editparams.cgi page
- via the web.
-
-
- The value of the cookiepath parameter should be the actual directory
- containing your Bugzilla installation, as seen by the
- end-user's web browser. Leading and trailing slashes are
- mandatory. You can also set the cookiepath to any directory which
- is a parent of the Bugzilla directory (such as '/', the root
- directory). But you can't put something that isn't at least
- a partial match or it won't work. What you're actually doing
- is restricting the end-user's browser to sending the cookies
- back only to that directory.
-
-
- How do you know if you want your specific Bugzilla directory or the
- whole site?
-
-
-
- If you have only one Bugzilla running on the server, and you
- don't mind having other applications on the same server with it
- being able to see the cookies (you might be doing this on purpose
- if you have other things on your site that share authentication with
- Bugzilla), then you'll want to have the cookiepath set to "/", or to
- a sufficiently-high enough directory that all of the involved apps
- can see the cookies.
-
-
- Examples:
-
-
-
- urlbase is
- cookiepath is /
-
- urlbase is
- but you have http://tools.mysite.tld/someotherapp/ which shares
- authentication with your Bugzilla
- cookiepath is /
-
-
-
-
-
- On the other hand, if you have more than one Bugzilla
- running on the server (some people do - we do on landfill)
- then you need to have the cookiepath restricted enough
- so that the different Bugzillas don't
- confuse their cookies with one another.
-
-
- Examples:
-
-
-
- urlbase is
- cookiepath is /bugzilla-tip/
-
- urlbase is
- cookiepath is /bugzilla-2.16-branch/
-
-
-
-
-
- If you had cookiepath set to / at any point in the past and
- need to set it to something more restrictive (i.e. /bugzilla/),
- you can safely do this without requiring users to delete
- their Bugzilla-related cookies in their browser (this is
- true starting with Bugzilla 2.17.7 and Bugzilla 2.16.5).
-
-
-
-
-
-
-
- Why do users have to log in every time they access a page? This
- only seems to affect some of my Bugzilla's users, others stay
- logged in.
-
-
-
-
- First, make sure cookies are enabled in the user's browser.
-
-
- If that doesn't fix the problem, it may be that
- the user's ISP implements a rotating proxy server. This causes
- the user's effective IP address (the address which the Bugzilla server
- perceives him coming from) to change periodically. Since
- Bugzilla cookies are tied to a specific IP address, each time
- the effective address changes, the user will have to log in again.
-
-
- In newer versions of Bugzilla (2.17.1 and later) there is a
- parameter called "loginnetmask", which you can use to set the
- number of bits of the user's IP address to require to be matched
- when authenticating the cookies. If you set this to something less
- than 32, then the user will be given a checkbox for "Restrict this
- login to my IP address" on the login screen, which defaults to
- checked. If they leave the box checked, Bugzilla will behave the
- same as it did before, requiring an exact match on their IP address
- to remain logged in. If they uncheck the box, then only the left
- side of their IP address (up to the number of bits you specified in
- the parameter) has to match to remain logged in.
-
-
-
-
@@ -719,12 +596,19 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl
(I've followed the instructions in the installation section of this guide)?
+
Run MySQL like this: "mysqld --skip-grant-tables". Please remember this
makes MySQL as secure as taping a $100 to the floor of a football stadium
bathroom for safekeeping.
+
+ This can't be stressed enough. Doing this is a bad idea.
+ Please consult of this guide and
+ the MySQL documentation for better solutions.
+
+
--
cgit v1.2.3-24-g4f1b