[Kolab-devel] [issue3322] freebusy.conf.template: ldap server can be on another machine

Mathieu Parent kolab-issues at intevation.de
Tue Dec 16 16:45:10 CET 2008


New submission from Mathieu Parent <mathieuparent at users.sourceforge.net>:

Current configuration of freebusy connects to local host (fqdn). This is good
because readonly access is sufficient (as available on slave LDAP servers).

but ;)

If the LDAP server(s) are on another machine, it failed. The attached patch
makes it always connect to ldap master.

Is this OK to apply it?

----------
assignedto: mathieu.parent
files: freebusy.conf.template.in.diff
messages: 18102
nosy: mathieu.parent, rbos, thomas, wrobel
priority: feature
status: unread
title: freebusy.conf.template: ldap server can be on another machine
topic: freebusy, patch, server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3322>
___________________________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: freebusy.conf.template.in.diff
URL: <http://lists.kolab.org/pipermail/devel/attachments/20081216/b715f56b/attachment.ksh>


More information about the devel mailing list