thomas: doc/raw-howtos kolab_2.0_to_2.1_upgrade_instructions.txt, 1.10, 1.11

[cvs at kolab.org]

Author: thomas

Update of /kolabrepository/doc/raw-howtos
In directory doto:/tmp/cvs-serv12320

Modified Files:
	kolab_2.0_to_2.1_upgrade_instructions.txt 
Log Message:
Indicate root or user for commands. Use umask 077 for handling ldifs.
(on many systems /root is world-readable)


Index: kolab_2.0_to_2.1_upgrade_instructions.txt
===================================================================
RCS file: /kolabrepository/doc/raw-howtos/kolab_2.0_to_2.1_upgrade_instructions.txt,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- kolab_2.0_to_2.1_upgrade_instructions.txt	20 Feb 2007 14:35:32 -0000	1.10
+++ kolab_2.0_to_2.1_upgrade_instructions.txt	19 Apr 2007 09:41:44 -0000	1.11
@@ -15,27 +15,29 @@
 
 1. Stop the Kolab Server and related cronjobs:
 
-    Comment out all OpenPKG entries in /etc/crontab, then run:
+   Comment out all OpenPKG entries in /etc/crontab, then run:
 
-    /kolab/bin/openpkg rc all stop
+    # /kolab/bin/openpkg rc all stop
 
 2. Backup the old installation:
 
-    You could use rsync on the running server and then rsync again
-    to transfer only changed files to keep the downtime short.
+   You could use rsync on the running server and then rsync again
+   to transfer only changed files to keep the downtime short.
 
 3. Extract ldap data:
 
-    Copy the contents of the openldap database (use a different output
-    filename if you want):
+   Copy the contents of the openldap database, use a different output
+   filename if you want. You should make sure that no other users can
+   read the sensitive data contained in the ldif file, e.g. with umask:
 
-    /kolab/sbin/slapcat > ~/kolab-2.0.ldif
+    # umask 077
+    # /kolab/sbin/slapcat > ~/kolab-2.0.ldif
 
 4. Prepare for berkeley db update
 
-    cd /kolab/var/imapd/db
-    /kolab/bin/db_recover
-    rm /kolab/var/imapd/db/*
+    # cd /kolab/var/imapd/db
+    # /kolab/bin/db_recover
+    # rm /kolab/var/imapd/db/*
 
 
 Installation
@@ -61,7 +63,7 @@
 renamed.  There might be more files with the .rpmsave ending in
 /kolab/etc, you can find them for example using the find command:
 
-find /kolab/etc -name '*.rpmsave'
+    # find /kolab/etc -name '*.rpmsave'
 
 Any files found must be checked and moved out of the way, in most
 cases they can just be deleted.
@@ -94,15 +96,15 @@
 
 To convert the databases to berkeley db format, execute as root:
 
-su - kolab-r
-cd /kolab/var/imapd/
-mv annotations.db annotations.db-skiplist
-/kolab/bin/cvt_cyrusdb /kolab/var/imapd/annotations.db-skiplist skiplist \
-                       /kolab/var/imapd/annotations.db berkeley
-mv mailboxes.db mailboxes.db-skiplist
-/kolab/bin/cvt_cyrusdb /kolab/var/imapd/mailboxes.db-skiplist skiplist \
-                       /kolab/var/imapd/mailboxes.db berkeley
-exit
+    # su - kolab-r
+    $ cd /kolab/var/imapd/
+    $ mv annotations.db annotations.db-skiplist
+    $ cvt_cyrusdb /kolab/var/imapd/annotations.db-skiplist skiplist \
+                  /kolab/var/imapd/annotations.db berkeley
+    $ mv mailboxes.db mailboxes.db-skiplist
+    $ cvt_cyrusdb /kolab/var/imapd/mailboxes.db-skiplist skiplist \
+                  /kolab/var/imapd/mailboxes.db berkeley
+    $ exit
 
 See http://wiki.kolab.org/index.php/Kolab2_IMAPD_annotations.db_Problems
 for details about this topic.
@@ -136,13 +138,14 @@
 The script works on the ldif data that was exported with slapcat earlier,
 it requires python-ldap:
 
-   python convert-ldif-21.py ~/kolab-2.0.ldif ~/kolab-2.1.ldif
+    # umask 077
+    # python convert-ldif-21.py ~/kolab-2.0.ldif ~/kolab-2.1.ldif
 
 
 Then restore the openldap data using the output from convert-ldif-21.py:
 
-   rm /kolab/var/openldap/openldap-data/*
-   /kolab/sbin/slapadd -l ~/kolab-2.1.ldif
+    # rm /kolab/var/openldap/openldap-data/*
+    # /kolab/sbin/slapadd -l ~/kolab-2.1.ldif
 
 This will issue some warnings which can be safely ignored.
 
@@ -151,8 +154,8 @@
 
 Now start the openldap server and run kolabconf
 
-    /kolab/bin/openpkg rc openldap start
-    /kolab/sbin/kolabconf
+    # /kolab/bin/openpkg rc openldap start
+    # /kolab/sbin/kolabconf
 
 
 Kolabconf might complain about be some files ending .rpmnew under
@@ -165,7 +168,7 @@
 
 Now you should be able to start the server again:
 
-    /kolab/bin/openpkg rc all start
+    # /kolab/bin/openpkg rc all start
 
 
 Resource Accounts
@@ -180,7 +183,7 @@
 done using the convert-ldif-21.py script, which was introduced in the
 section on converting the LDAP data.
 
-  python convert-ldif-21.py --list-resources ~/kolab-2.0.ldif
+    # python convert-ldif-21.py --list-resources ~/kolab-2.0.ldif
 
 lists the UIDs (normally the email addresses) of all resource accounts.
 
@@ -190,14 +193,14 @@
 
 Connect with cyradm to the Kolab imap server as user manager:
 
-  /kolab/bin/cyradm -u manager localhost
+    # /kolab/bin/cyradm -u manager localhost
 
 Then use the `setaclmailbox' command (sam) to set the necessary
 permissions.  You can generate a list of commands which should do the
 right thing on most standard installations with:
 
-  python convert-ldif-21.py --list-resources ~/kolab-2.0.ldif | \
-  sed 's-\(.*\)\(@.*\)-sam */\1*\2 calendar\2 all-'
+    # python convert-ldif-21.py --list-resources ~/kolab-2.0.ldif | \
+      sed 's-\(.*\)\(@.*\)-sam */\1*\2 calendar\2 all-'
 
 
 Final Steps
@@ -212,7 +215,7 @@
 2. Kolab 2.1 doesn't need some of the OpenPKG packages which were
    installed for 2.0, these can be removed:
 
-   /kolab/bin/openpkg rpm -e dcron vim pth
+    # /kolab/bin/openpkg rpm -e dcron vim pth
 
    Especially the dcron package should be removed in any case,
    otherwise deprecated cronjobs will be run and generate mails with