thomas: server README.1st,1.56,1.57

cvs at kolab.org cvs at kolab.org
Thu May 10 12:17:39 CEST 2007


Author: thomas

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

Modified Files:
	README.1st 
Log Message:
Updated README for 2.1.0


Index: README.1st
===================================================================
RCS file: /kolabrepository/server/README.1st,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -d -r1.56 -r1.57
--- README.1st	2 May 2007 13:48:54 -0000	1.56
+++ README.1st	10 May 2007 10:17:37 -0000	1.57
@@ -91,8 +91,8 @@
 configuration files are regenerated from your templates.
 
 
-Upgrade from 2.0 releases to 2.1-versions
------------------------------------------
+Upgrade from Kolab server 2.0 to 2.1
+------------------------------------
 
 Upgrading from Kolab 2.0.x to 2.1 is described in detail in the file
 UPGRADING.20-21 in this directory.
@@ -280,20 +280,15 @@
 The database backend for the free/busy cache was changed to solve licensing
 issues between php4+ and gdbm. See kolab/issue1607 for details.
 
-The old cache file has to be deleted manually:
+Follow the steps to regenerate the free/busy cache shown in the section
+"Final Steps" in the file UPGRADING.20-21
 
-  rm /kolab/var/kolab/www/freebusy/cache/pfbcache.db
 
-Then updating the free/busy cache has to be triggered for all calendar
-folders of all accounts:
-- Users need to create or update an appointment in their folders.
-- Resources can be invited to a new appointment or send them an update
-  to an existing appointment.
+Upgrade from 2.1-rc-2
+---------------------
+
+Nothing special has to be done for this upgrade.
 
-Alternatively you can trigger each folder with an https request:
-https://[server]/freebusy/trigger/[email]/[path_to_calendar_folder].pfb,
-e.g. https://kolab.example.com/freebusy/trigger/user@example.com/Calendar.pfb
-(you need to authenticate with the user's credentials)
 
 
 Known problems and workarounds





More information about the commits mailing list