thomas: server release-notes.txt,1.102,1.103 README.1st,1.54,1.55

[cvs at kolab.org]

Author: thomas

Update of /kolabrepository/server
In directory doto:/tmp/cvs-serv20482

Modified Files:
	release-notes.txt README.1st 
Log Message:
Documented workaround for libdb3 conflict in README.1st (kolab/issue1607)


Index: release-notes.txt
===================================================================
RCS file: /kolabrepository/server/release-notes.txt,v
retrieving revision 1.102
retrieving revision 1.103
diff -u -d -r1.102 -r1.103
--- release-notes.txt	20 Apr 2007 15:28:28 -0000	1.102
+++ release-notes.txt	24 Apr 2007 16:19:11 -0000	1.103
@@ -34,6 +34,11 @@
       For details see kolab/issue1089.
 
 
+Changes since 2.1 rc 2:
+
+    Documented workaround for libdb3 conflict in README.1st
+
+
 Changes since 2.1 rc 1:
 
     - apache-1.3.33-2.5.6_kolab2

Index: README.1st
===================================================================
RCS file: /kolabrepository/server/README.1st,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -d -r1.54 -r1.55
--- README.1st	20 Apr 2007 10:24:31 -0000	1.54
+++ README.1st	24 Apr 2007 16:19:11 -0000	1.55
@@ -294,6 +294,33 @@
       a UTF-8 locale, e.g. ja_JP.UTF-8 for Japanese.
       See kolab/issue881 and kolab/issue1585 for details.
 
+    - If login on https://yourserver.example.com/fbview and triggering
+      free/busy regeneration does not work, try as user kolab:
+
+        /kolab/bin/php -r 'imap_open("{localhost:143/notls}", "" ,"");'
+
+      If it yields "Segmentation fault (core dumped)", then there probably is
+      a conflict between a dynamically loaded libdb3 from your system and a
+      statically linked libdb4 from the OpenpPKG php package. If it yields a
+      "PHP Warning: ...", this part of the system works correctly.
+
+      One reason for such a conflict could be the mere presence of
+      /lib/libnss_db.so.*, which is installed on some distributions by
+      default. On Debian systems it is contained in the package "libnss-db".
+      If you really need this library, you could work around the loading of
+      libdb3 by placing a symbolic link with the correct name in /kolab/lib,
+      e.g.:
+
+        ldd /lib/libnss_db.so.2
+                libnss_files.so.2 => /lib/tls/libnss_files.so.2 (0xb7f16000)
+           ---> libdb3.so.3 => /usr/lib/libdb3.so.3 (0xb7e6b000)
+                libc.so.6 => /lib/tls/libc.so.6 (0xb7d36000)
+                /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
+        ln -s /dev/null /kolab/lib/libdb3.so.3
+
+      See kolab/issue1607 (need to replace gdbm for pfbcache, because of
+      license clash gdbm vs php) for details.
+
     - Under some circumstance the Kolab server may not create or delete
       users or update the configuration after changes have been made in
       the web interface.  This happens most often immediately after the