[Kolab-devel] Re: Kolab Build System - input required

[Bo Thorsen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 02 September 2003 22:09, Stephan Buys wrote:
> Thanks for the feedback!
>
> On Tuesday 02 September 2003 21:46, you wrote:
> > First of all: having the domain/hostname in the configure line makes
> > it impossible to reconfigure the server without recompilation. That's
> > a bad idea.
>
> Okay, the hostname is usually handled in the bootstrap script anyway,
> so this is probably not a good idea for a switch.
>
> >A related problem is in the way the network setup is done - I spent
> > an hour or two yesterday trying to figure out how to make the setup
> > figure out that my server got a new IP number (I ended up having to
> > completely wipe out openldap, and reinstall it).
> >
> :-) Did you hostname change? There shouldn't be a problem with an IP
> address change, only with the BASE DN of the all the objects in Kolab.
> Early QIM's handle how to update all the objects for a reimplementation
> of LDAP.

There is a problem. From postfix/main.cf:

mynetworks = 127.0.0.0/8, 129.142.192.0/20, 192.168.1.0/24

The middle one used to be my old network, and before I delete all files in 
/kolab/var/openldap, nothing I did would change it to the new values.

My "solution":

# /kolab/bin/rpm -r --nodeps openldap2
# rm -rf /kolab/var/openldap
# /kolab/bin/rpm -ba openldap2
# /kolab/bin/rpm -Uvh openldap2
# /kolab/etc/kolab/kolab_bootstrap -b

(All from memory, so I'm sure I left out some details.)

Bo.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE/VYI8mT99lwfUS5IRAmYWAJ9mAPWqqhGj17m1f/By2lBtTYgcVACfcjeq
nU7yF9G3R1ooS6vvDUhe3uI=
=Jnj3
-----END PGP SIGNATURE-----