summaryrefslogtreecommitdiff
path: root/docs/modpython.txt
diff options
context:
space:
mode:
authorAdrian Holovaty <adrian@holovaty.com>2006-02-16 03:55:48 +0000
committerAdrian Holovaty <adrian@holovaty.com>2006-02-16 03:55:48 +0000
commitc1dded685d5c2588f688fe45524b8d51e766075b (patch)
tree323a8e56eee35e79ec5daa7db05ed4d1e8965307 /docs/modpython.txt
parentf732217c0a80d055976497a9c07c330db0ae76bb (diff)
Added 'If you get a segmentation fault' to docs/modpython.txt
git-svn-id: http://code.djangoproject.com/svn/django/trunk@2309 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/modpython.txt')
-rw-r--r--docs/modpython.txt10
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/modpython.txt b/docs/modpython.txt
index baa534ae91..3a48967a57 100644
--- a/docs/modpython.txt
+++ b/docs/modpython.txt
@@ -198,3 +198,13 @@ that case, you'll see an "Internal Server Error" page in your browser and the
full Python traceback in your Apache ``error_log`` file. The ``error_log``
traceback is spread over multiple lines. (Yes, this is ugly and rather hard to
read, but it's how mod_python does things.)
+
+If you get a segmentation fault
+===============================
+
+If Apache causes a segmentation fault, it's probably because you're running
+mod_python and mod_php in the same Apache instance, with MySQL as your database
+backend. This is a known mod_python issue, not a Django issue, and there's more
+information in the `mod_python FAQ entry`.
+
+.. _mod_python FAQ entry: http://modpython.org/FAQ/faqw.py?req=show&file=faq02.013.htp