[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
next_id_read?
Hello,
Using openldap-1.2.9 I sometimes encounter some weird messages when
building the ldbm databases (LDBM via Berkeley DB2):
,-----
| dvl@freeman:~/ldap-prov/project/bindist/linux-2.2$ /home/dvl/ldap-prov/project/bindist/linux-2.2/bin/ldif2ldbm -f /tmp/test-ldap-ctrl/create-ldbm/create-ldbm.conf -s /home/dvl/ldap-prov/project/bindist/linux-2.2/bin -j 9 -d 512 -i /tmp/sample.ldif
| id 1035 already in next block
| id 1035 already in next block
| id 1035 already in next block
`-----
and (the db directory is initially empty):
,-----
| dvl@freeman:~/ldap-prov/project/bindist/linux-2.2$ /home/dvl/ldap-prov/project/bindist/linux-2.2/bin/ldif2ldbm -f /tmp/test-ldap-ctrl/create-ldbm/create-ldbm.conf -s /home/dvl/ldap-prov/project/bindist/linux-2.2/bin -j 9 -d 512 -i /tmp/sample.ldif
| next_id_read: could not open "/tmp/test-ldap-ctrl/create-ldbm/run/NEXTID"
| next_id_read: could not open "/tmp/test-ldap-ctrl/create-ldbm/run/NEXTID"
| next_id_read: could not open "/tmp/test-ldap-ctrl/create-ldbm/run/NEXTID"
| id 1035 already in next block
| id 1035 already in next block
| id 1035 already in next block
`-----
Is this a serious problem, or intended behaviour. The resulting
database files seem to work.....
Regards,
Dirk
--
Dirk.Vleugels@de.uu.net http://www.de.uu.net
Database Engineer UUNET Deutschland GmbH