Re: [Lurker-users] lurker-regenerate fixes the segfaults, but...

[Aleksandr M. <n6...@mi...>]

Aleksandr Milewski wrote:
> Aleksandr Milewski wrote:
>> ...still destroys the date on anything imported with -u.
> 
> So, I didn't realize that lurker-regenerate is just a script that's 
> wrapped around lurker-index, and it calls it without -u, so of course 
> this happens.

I just hacked up a version of lurker-regenerate that uses lurker-index 
-u. Call it lurker-regenerate-u.

I imported all the messages that have no 'From ' line into a fresh 
database. This database causes lurker.cgi to segfault.

I ran lurker-regenerate-u over it. It still segfaults.

I ran lurker-regenerate over it...no segfault.

So there's something broken in importing with -u, somehow. As I've said 
before, I'm pretty sure it's not a poison message, as if I go through 
these archives in small blocks until I start getting segfaults, I can 
import that last block by itself and everything's fine.

I'm now wondering if it's something silly like 64k records with the same 
timestamp or something.

Back to see if I can figure out how to make lurker-index -u write the 
user timestamp into the synthetic 'From ' line.

-Z