thomas: server README.1st,1.44,1.45 release-notes.txt,1.80,1.81

cvs at kolab.org cvs at kolab.org
Mon Feb 5 15:29:54 CET 2007


Author: thomas

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

Modified Files:
	README.1st release-notes.txt 
Log Message:
Moved "Known Problems" section to README.1st


Index: README.1st
===================================================================
RCS file: /kolabrepository/server/README.1st,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -d -r1.44 -r1.45
--- README.1st	18 Jan 2007 14:06:43 -0000	1.44
+++ README.1st	5 Feb 2007 14:29:52 -0000	1.45
@@ -3,6 +3,7 @@
 
 For more information on Kolab, see http://www.kolab.org
 
+
 Quick install instructions
 --------------------------
 
@@ -268,6 +269,36 @@
 -----------------------
 
 Nothing special has to be done for this upgrade.
+
+
+Known problems and workarounds
+------------------------------
+
+    - Under some circumstance the Kolab server may not update create
+      users or update the configuration after changes have been made in
+      the web interface.  This happens most often immediately after the
+      bootstrap.  In that case restart the kolabd:
+
+        /kolab/bin/openpkg rc kolabd restart
+
+      See kolab/issue1068 (Mailboxes are not created until kolabd restart)
+      and kolab/issue1098 (Changes in the service tab are not accepted after
+      bootstrap) for details.
+
+    - If modifying or deleting of address book entries doesn't work,
+      restarting openldap can help, see kolab/issue854 for details.
+
+    - There is a report that the manager can only see users in the primary
+      domain, see kolab/issue1485. We can't reproduce this problem, please
+      tell us if you can.
+
+    - Calendar folders for group/resource accounts can't be created for
+      domains which were added after bootstrap, i.e. via the web admin
+      interface. See kolab/issue1313 for details.
+
+    - When deleting domains via the web admin interface, the corresponding
+      LDAP data and IMAP spool stay on the server and have to be deleted
+      manually. See kolab/issue1571 and kolab/issue1576 for details.
 
 
 $Id$

Index: release-notes.txt
===================================================================
RCS file: /kolabrepository/server/release-notes.txt,v
retrieving revision 1.80
retrieving revision 1.81
diff -u -d -r1.80 -r1.81
--- release-notes.txt	5 Feb 2007 13:55:43 -0000	1.80
+++ release-notes.txt	5 Feb 2007 14:29:52 -0000	1.81
@@ -35,35 +35,6 @@
       For details see kolab/issue1089.
 
 
-Known problems:
-
-    - Under some circumstance the Kolab server may not update create
-      users or update the configuration after changes have been made in
-      the web interface.  This happens most often immediately after the
-      bootstrap.  In that case restart the kolabd:
-
-	/kolab/bin/openpkg rc kolabd restart
-
-      See kolab/issue1068 (Mailboxes are not created until kolabd restart)
-      and kolab/issue1098 (Changes in the service tab are not accepted after
-      bootstrap) for details.
-
-    - If modifying or deleting of address book entries doesn't work,
-      restarting openldap can help, see kolab/issue854 for details.
-
-    - There is a report that the manager can only see users in the primary
-      domain, see kolab/issue1485. We can't reproduce this problem, please
-      tell us if you can.
-
-    - Calendar folders for group/resource accounts can't be created for
-      domains which were added after bootstrap, i.e. via the web admin
-      interface. See kolab/issue1313 for details.
-
-    - When deleting domains via the web admin interface, the corresponding
-      LDAP data and IMAP spool stay on the server and have to be deleted
-      manually. See kolab/issue1571 and kolab/issue1576 for details.
-
-
 Changes since 2.1 beta 4:
 
     - kolabd-2.0.99-20070205





More information about the commits mailing list