search for: skip_duplicates

...39;t updated, in replace duplicates mode (so that > multiple runs of omindex on different subsites don't stomp on each > other). This fix seems to be avoiding the real issue, so it's less than ideal I feel. Looking at the code, what it's really doing is turning off half of "skip_duplicates" - the bit at the end of the run where we delete any documents we've not seen (on the assumption that they've been deleted from the document tree since the previous index run). (Although I notice it still creates and updates the bitmap we use to track deleted documents, but that's...