expireover core (perhaps an ov3search bug)

[Christophe Wolfhugel]

I'm pretty sure that INN is not responsible for such a corrupted index
but it is rather due to a good old kernel crash.

While removing the files is probably the thing to do, shall this just be
included in expireover :

  if (offset + length > end of memory zone)
     unlink the files, they're probably useless anyway
     print a diag somewhere

... and have an external program <to-be-done> redo the overview files,
eventually.

Russ Allbery :
> What I'm not understanding is how it's getting corrupted in the first
> place.  The index entry is clearly wrong, and it's being read directly out
> of the file.  But the only places that write index entries are OV3addrec
> and OV3packgroup, and when expire is running the index and overview files
> are being written to new files that only replace the old files after
> they've been successfully written.

-- 
Christophe Wolfhugel  -+-  wolf at oleane.net  -+-  France Telecom Oleane