[Kolab-devel] [issue1092] Kolab serious "kolabconf" problem on high number of openldap users

[Fabio Pietrosanti / Khamsa SA]

New submission from Fabio Pietrosanti / Khamsa SA <kolab at khamsa.ch>:

Kolabconf under a high number of users seems to have some problem because it crawl the whoole 
directory with filter=* for 3 different unused functions.

Search for the string “filter” and find every filter that’s not enought strict that cause a lot of time 
neededs to crawl an ldap directory (with a lot of  cpu and memory usage seriously impacting the 
system)

- function buildCyrusGroups
never write anything, at least for what can be configured from the webadmin interface to the file that's 
it's configuration file target: /kolab/etc/imapd/group
it has performance problematic "filter => '(objectClass=*)' );"

Commenting
#buildCyrusGroups;
solved the problem.

- function buildPostfixMap

never write anything, at least for what can be configured from the webadmin interface to the file that's 
it's configuration file target: /kolab/etc/postfix/transport and /kolab/etc/postfix/virtual
it has the performance problematic "filter => '(objectClass=*)' );"


Commenting
#    buildPostfixMap( 'transport' );
#    buildPostfixMap( 'virtual' );
solved the problem

I'm wondering wether those function commented out would cause problem within actual kolab 
installation.

----------
messages: 6391
nosy: khamsa
status: unread
title: Kolab serious "kolabconf" problem on high number of openldap users
________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://intevation.de/roundup/kolab/issue1092>
________________________________________________