Before changing over to "mdb" from "bdb", I ran a script that used slapcat to generate an LDIF file every night. Since updating to "mdb", that script fails if "slapd" is running. That is expected behavior from what I have been reading. http://www.openldap.org/faq/data/cache/288.html
My question is how do I export the directory into an LDIF file if "slapd" is running, or is that not supported? I could easily modify the script to shut down the program, backup the directory in an LDIF format and restart the program; however, that seems overly ambitious. I understand that "replication" is an option, but I don't know if I really want to go that route at this time.
Hi,
On Sat, 8 Nov 2014, Jerry wrote:
Before changing over to "mdb" from "bdb", I ran a script that used slapcat to generate an LDIF file every night. Since updating to "mdb", that script fails if "slapd" is running. That is expected behavior from what I have been reading. http://www.openldap.org/faq/data/cache/288.html
No.
That documentation refers to the age old and long deprecated backend that preceeded both berkeley db backends.
My question is how do I export the directory into an LDIF file if "slapd" is running, or is that not supported? I could easily modify the script to shut down the program, backup the directory in an LDIF format and restart the program; however, that seems overly ambitious. I understand that "replication" is an option, but I don't know if I really want to go that route at this time.
just run slapcat. It should work just fine. If not provide more details.
Greetings Christian
Jerry,
Jerry schrieb (08.11.2014 13:07 Uhr):
Before changing over to "mdb" from "bdb", I ran a script that used slapcat to generate an LDIF file every night. Since updating to "mdb", that script fails if "slapd" is running. That is expected behavior from what I have been reading. http://www.openldap.org/faq/data/cache/288.html
ldbm <> mdb|lmdb
Marc
openldap-technical@openldap.org