Jonas,
	Sorry, I'd missed this message earlier.

Jonas Meurer wrote:

> I don't know what your particular error messages do mean in detail, but I
> know that lurker runs on systems with many, many more archived messages.

I'd love to know how. Is it just you and me on this list? The issue with 
lurker-regenerate is still going to be a problem if I can get past this 
segfault. I was hoping to hear something from a developer. It seems that 
Lurker is unmaintained at this point... the lurker lurking on 
lurker-users hasn't been updated in 9 months.

> You get your ulimit values by executing 'ulimit -a'. You can also adjust
> the values with the ulimit utility.

Sure, those are *my* ulimit values. How do I control the ulimit values 
that apache is running under? I'm actually less convinced that this is 
the problem. I suspect that this is just a bug in Lurker, and possibly 
one exposed by running it on a 64bit system.

The machine in question is running Ubuntu Gutsy (7.10) amd64 on two 
quad-core Xeons (E5310...cheap, slow cores, but lots of them :D) with 
2GB of RAM.



-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Lurker-users mailing list
Lurker-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lurker-users