New server

[Thomas Arendsen Hein]

* Roy Hoobler <roy at connectcomputing.com> [20060125 14:50]:
> We had /kolab on a seperate hard drive.  The / drive was
> compromised so we are installing the OS on a new drive.
> 
> What is the quickest way to get /kolab up and running again?
> Will ./obmtool work?  The system is live and keeping the data safe is of most 
> importance.  I'll only have a couple of hours to make sure everything is 
> good.

Move your existing /kolab out of the way, run obmtool. You can abort
installation as soon as the first package was installed. This
creates the three kolab users (kolab, kolab-r, kolab-n) and some
files in /etc.

Now remove the newly created /kolab directory and move your old copy
back. Verify that the files are owned by the newly created kolab
users.

Now everything should be fine again and you can start your server.

Thomas

-- 
Email: thomas at intevation.de
http://intevation.de/~thomas/