From 49e128bc5105aea5c9306a6ce3c0ea06a77f9c34 Mon Sep 17 00:00:00 2001
From: "cyeh%bluemartini.com" <>
Date: Sat, 17 Feb 2001 02:07:54 +0000
Subject: fix for 68873 : Bugzilla install doesn't work over NFS; mention this
 in README patch submitted by tstromberg@rtci.com (Thomas Stromberg).

---
 README | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

(limited to 'README')

diff --git a/README b/README
index e52e2c847..cf40ba77f 100644
--- a/README
+++ b/README
@@ -52,6 +52,9 @@ news://news.mozilla.org/19990913183810.SVTR29939.mta02@onebox.com
    Bugzilla has quite a few prerequisites, but none of them are TCL.
 Previous versions required TCL, but it no longer needed (or used).
 
+   You must also run Bugzilla on a filesystem that supports file locking via
+flock(). This is necessary for Bugzilla to operate safely with multiple instances.
+
 1.1. Getting and setting up MySQL database (3.22.5 or greater)
 
    Visit MySQL homepage at http://www.mysql.org and grab the latest stable
@@ -306,8 +309,14 @@ The first time you run it, it will create a file called "localconfig"
 which you should examine and perhaps tweak a bit.  Then re-run
 checksetup.pl and it will do the real work.
 
+It's worth noting that ./checksetup.pl will stall if it is on a filesystem
+that does not fully support file locking via flock(), such as NFS mounts.
+This support is required for Bugzilla to operate safely with multiple
+instances. If flock() is not fully supported, it will stall at:
+
+   "Now regenerating the shadow database for all bugs."
 
-At ths point, you should have a nearly empty copy of the bug tracking
+Should everything work, you should have a nearly empty copy of the bug tracking
 setup.
 
 4. Tweaking the Bugzilla->MySQL Connection Data
-- 
cgit v1.2.3-24-g4f1b