Ldap changes with upgrade from 2.2.4 to 2.3.4

[Christoph Wickert]

On Tuesday 15 November 2011 18:06:15 John McMonagle wrote:
> On Tuesday 15 November 2011 10:47:14 am Christoph Wickert wrote:
>
> > Hi John,
> > 
> > I'm sorry, this is a part I don't understand: You have several LDAP
> > servers but the Kolab-server is the master for all of them?
> 
> Actually  kolab's ldap is disabled and I'm using slapd in the lenny host.
> Doctored up slapd.conf as required. It's a slave of the advocap master ldap
> server and it also acts as a master for kolab.

OK, this all makes sense. Our default config assumes that Kolab is a 
standalone service, but as soon as you have several users of the LDAP, I 
usually suggest to switch to another server and make Kolab a slave. That other 
server is best provided by the distribution.

Future setup scripts will be more flexible to better integrate into existing 
infrastructures. 

Regards,
Christoph

-- 
Christoph Wickert
Senior Engineer

Kolab Systems AG
Zürich, Switzerland

e: wickert at kolabsys.com
t: +49 251 871 369 77
w: http://kolabsys.com

pgp: 85DACC63 Christoph Wickert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/users/attachments/20111115/6fb95e2a/attachment.sig>