--On Saturday, May 18, 2019 9:48 AM +0000 james@turnersoft.co.uk wrote:
Full_Name: James Turner Version: 2.4 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (81.86.27.193)
As OpenLDAP 2.4, system administrators have to make sure that they configure the correct order in which modules are loaded during sever startup. (e.g. load "back_monitor" last, "auditlog" typically second from last). Configuring this order incorrectly often prevents the server from starting up, or modules from functioning as expected.
I've never encountered a situation where the order in which moduleload executes matters. Can you please provide an example configuration exhibiting problematic behavior based on moduleload order?
Thanks, Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com