[Mailman-Users] qrunner lock

Jon Carnes jonc at nc.rr.com
Mon Oct 7 16:47:52 CEST 2002

This one should be in the FAQ if it is not already.

This is normal in Mailman version 2.0.x which you are *probably* running
(you didn't tell us your version or really anything about your system -
shame on you!)

This version of Mailman uses a cron job to launch qrunner every minute -
but if qrunner is still running from the previous minute, then it will
not be able to acquire a lock and it will not launch a second incident
of qrunner.

Why is qrunner still running?  Well its delivering mail to folks on your
mailing lists. As your lists grow larger qrunner takes longer to run.

Jon Carnes

On Mon, 2002-10-07 at 10:36, Chris Lawson wrote:
> Hi. 
> My qrunner log (in /var/log/mailman) is generating hundreds of lines like
> the following:
> Oct 07 10:33:04 2002 (6942) Could not acquire qrunner lock
> What is trying to lock qrunner? Why would it be failing to acquire a lock?
> What would be the consequences of failing to acquire a lock?
> cmkl
> -- 
> Chris Lawson
> clawson at jungle.ca
> http://www.jungle.ca
> ------------------------------------------------------
> Mailman-Users mailing list
> Mailman-Users at python.org
> http://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

More information about the Mailman-Users mailing list