I'm curious if anyone is using the control patch in a clustered setup, and if so have you changed the tree layout at all?
The default configuration is one cn for each host. In a clustered setup with 50+ servers each sharing some common info there is a lot duplicated entries. Has anyone considered an option to store shared data in a common portion of the tree? >From the patch: +The 'cn=' entry is the FQDN (Fully Qualified Domain Name, ie the full +hostname+domainname) of the host qmail is running on. We sort the +entries under each 'cn=<FQDN>,<controldn>' in our database so that we +can have multiple configurations for multiple qmail servers in the +same database under the same branch. Maybe something like instead: dn: cn=clusterinfo,ou=qmailldap,o=org,c=us cn: clusterinfo objectClass: top objectClass: qmailControl locals: domain.com locals: example.com rcpthosts: domain.com rcpthosts: example.com dirMaker: /usr/local/bin/mkhome ldapBaseDN: ou=users,o=org,c=us dn: cn=mail1.domain.com,ou=qmailldap,o=org,c=us objectClass: top objectClass: qmailControl clusterDN: cn=clusterinfo,ou=qmailldap,o=org,c=us .... I understand this would require a schema change and all. The clusterDN would be present in hosts that are members of the qmail cluster. Otherwise the entry for that mail server simply has the normal control entries. I could be way off with this, so please correct me if I'm insane! ;) Frank Clements
smime.p7s
Description: S/MIME cryptographic signature
