Hi Petr, On Sun, May 29, 2005 at 10:30:34PM +0200, Petr Vandrovec wrote: > There is one problem, that DB_CONFIG is put (should be put...) in > /var/lib/ldap, not into backends which were switched from ldbm to bdb. > Something based on get_database_list is needed, like slapcat & slapadd > loops do...
Just implemented that for the next upload.
> Due to this subsequent slapadd failed on ~5th entry as it was run without
> any DB_CONFIG file. I had to copy DB_CONFIG from /usr/share/slapd myself.
That's hefty. It should not fail because of missing DB_CONFIG.
> And BTW, there is something wrong with this copy anyway - DB_CONFIG was not
> copied into /var/lib/ldap either (it is just directory with some old ldap
> database from April, and there is no DB_CONFIG here...).
It was only instantiated for new databases up to now. I just changed
that to include migrated databases.
> And what's worse, on rerunning configuration it skipped slapadd step, so
> I was left with /var/lib/slapd empty (besides DB_CONFIG file I just copied
> there). Fortunately rerunning 'slapadd <
> /var/backups/slapd-2.2.23-5/ou=usermap,o=cvut,c=cz.ldif' was done with its
> job in few minutes.
That's intended behaviour. If the last slapadd was successful the
scripts are not going to slapadd again.
Greetings
Torsten
signature.asc
Description: Digital signature
