ando@sys-net.it wrote:
h.b.furuseth@usit.uio.no wrote:
ando@sys-net.it writes:
- the index should be invalidated
- slapd, at the next manual startup, should complain about the need to
run slapindex first.
If it knows enough to complain, why not restart the indexing task?
There should be an option in doing that. In fact, I suspect running slapindex -q can be much more efficient than letting slapd index while serving without index. Of course, slapd cannot serve while slapindex'ing, so I think human intervention is needed to determine what's most appropriate on a case by case basis.
I suppose we should save the last entryID that was indexed at shutdown time, so that the indexer task can resume at the next startup. We'd also need some coordination with slapindex, so that if you ran slapindex after shutdown, it would erase the saved status. Rather than add any fields to the DB index files, it would probably be OK to write the status in the cn=config tree.