Module: sip-router
Branch: master
Commit: 77d81c02bf24b5ef266ad6dfecf393342cfe4000
URL:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=77d81c0…
Author: Carsten Bock <carsten(a)ng-voice.com>
Committer: Carsten Bock <carsten(a)ng-voice.com>
Date: Mon Feb 3 09:58:59 2014 +0100
presence: Clarify the db_lock_type in the docs in conjunction with the mode DB_ONLY and a
MySQL-Backend.
---
modules/presence/doc/presence_admin.xml | 12 +++++++++---
1 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/modules/presence/doc/presence_admin.xml
b/modules/presence/doc/presence_admin.xml
index 8b18174..e753463 100644
--- a/modules/presence/doc/presence_admin.xml
+++ b/modules/presence/doc/presence_admin.xml
@@ -578,9 +578,15 @@ modparam("presence", "fetch_rows", 1000)
<section>
<title><varname>db_table_lock_type</varname>
(integer)</title>
<para>
- Enable (=1) or disable (=0) the Locks for table during an transaction.
- Locking only the "current" table causes problems with a MySQL-Databases
- in "DB-Only" mode.
+ Enable (=1) or disable (=0) the Locks for table during an
+ transaction. Locking only the "current" table causes problems
+ with a MySQL-Databases in "DB-Only" mode.
+ </para>
+ <para>
+ In order to use the Presence-Module in "DB_ONLY"-mode with a
+ MySQL-Backend, set this parameter to "0", otherwise the
+ MySQL-Operations will fail. The Presence-Module will generate
+ a "500 Server error" due to the failed MySQL-queries.
</para>
<para>
<emphasis>