thomas: server README.1st,1.46,1.47

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


Author: thomas

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

Modified Files:
	README.1st 
Log Message:
Added more hints on rpmsave files (suggested by Johannes Graumann) and
remove obsolete information about checking file permissions.


Index: README.1st
===================================================================
RCS file: /kolabrepository/server/README.1st,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -d -r1.46 -r1.47
--- README.1st	5 Feb 2007 14:56:08 -0000	1.46
+++ README.1st	5 Feb 2007 15:16:52 -0000	1.47
@@ -50,22 +50,22 @@
 # ./obmtool kolab
 
 obmtool will usually automatically determine which packages need to be
-built.  If you have made changes to the configuration files in
-/kolab/etc/kolab/templates/ and the new release has a new kolabd package
-you may need to transfer your changes from the backups created by rpm
-(the *.rpmsave) files to the new template files.  Then regenerate the
-configuration with
+built.  If you have made changes to configuration files or an updated
+package includes configuration files which are usually regenerated from
+files in /kolab/etc/kolab/templates/ the old configuration file will be
+saved with the extension .rpmsave.  For files generated from templates
+you just have to remove the rpmsave file, because services will refuse
+to start if there still is an rpmsave file, e.g.:
 
-# /kolab/sbin/kolabconf
+# rm /kolab/etc/clamav/*.conf.rpmsave
 
+For other changed files (e.g. the template files themselves) you may
+want to transfer your changes from the .rpmsave backup to the new files.
 
-You may want to check the permissions of your files in /kolab/etc/kolab/
-after installing or upgrading, as there have been problems with this in
-the past.  Especially kolab.conf and copies shall only be readable to
-the owner (usually "kolab").  The installation and configuration scripts
-should make sure that the permissions are correct but there's a chance
-that the permissions can still go wrong, especially if you upgrade from
-pre Beta1 releases.
+Then regenerate the configuration and restart Kolab with:
+
+# /kolab/sbin/kolabconf
+# /kolab/bin/openpkg rc all restart
 
 
 Upgrading from earlier versions





More information about the commits mailing list