[Mailman-Users] Re: "could not acquire qrunner lock", etc (partially solved)

[Marc MERLIN]

On Sat, Apr 28, 2001 at 09:09:38PM +0100, Mike Crowe wrote:
> I've discovered the cause of the CPU usage problem. I had ARCHIVE_TO_MBOX
> set to the default of 2. It appears that the archiver eats an awful lot of
> processor power - so much that the backlog caused by the earlier bug was
> taking ages to clear. The qrunner would sit in the second part of
> ToArchive::process for around fifteen minutes whilst holding onto the list
> lock which stopped the web interface from working.

Yep, this is known, I've had  the same problem on several servers, including
sourceforge.net, which only has 2G of  memory a dual 800Mhz P3 or something,
so don't feel inferior with your machine, it's the code that's at fault :-)

The  good news  is that  the mm  folks know  about this  and redesigned  the
queueing system  to avoid this  holdup. All that said, pipermail  will still
not be an archiver of choice, you are encouraged to use something else.

Empegs rule! :-)
Marc
-- 
Microsoft is to operating systems & security ....
                                      .... what McDonalds is to gourmet cooking
  
Home page: http://marc.merlins.org/   |   Finger marc_f at merlins.org for PGP key