ITS#7906,#7923 Don't free configinfo in _db_close

[openldap] / servers / slapd / overlays / slapover.txt

diff --git a/servers/slapd/overlays/slapover.txt b/servers/slapd/overlays/slapover.txt
index 856016226aaf1b9f32d8a9d9646f559dc6215b89..2015d8da2a17d4d5d0af73edd85e6695de9ebdc7 100644 (file)
--- a/servers/slapd/overlays/slapover.txt
+++ b/servers/slapd/overlays/slapover.txt
@@ -149,4 +149,10 @@ servers to be cached locally. In both cases the overlays must provide a bit of
 glue to swap in the appropriate be_private and bd_info pointers before invoking
 the attached backend, which can then be invoked as usual.
 
+Note on overlay initialization/destruction: you should allocate storage for
+config info in the _db_init handler, and free this storage in the _db_destroy
+handler. You must not free it in the _db_close handler because a module may
+be opened/closed multiple times in a running slapd when using dynamic
+configuration and the config info must remain intact.
+
 ---