[Mailman-Developers] race condition in locking ?
Mon, 7 Feb 2000 20:43:31 +0100
On Sat, Feb 05, 2000 at 11:21:30PM +0100, Thomas Wouters wrote:
> On Sat, Feb 05, 2000 at 08:56:53PM +0100, Ricardo Kustner wrote (in private):
> > AssertionError:
> > if you need to see the logs/error or logs/lock files let me know...
> [ CC: the list, because of the questions at the bottom ]
> Hmmm. I think I found the problem, but I'm not entirely sure. It looks like
> the default MailList lock timeout is 60 seconds, and that that is too short
> for your machine. You should see some 'stolen!' or (in my LockFile version)
> 'broken!' messages, in your logs/locks file.
yes i did see "stolen!" in the logs just before the process was about to crash.
> In any case, you can easily try it out; in Mailman/MailList.py, on or around
> line 282, there should be a 'lifetime = 60', inside the constructor for the
> maillists' lockfile. Changing the '60' in, say, '600', should give you
thanks a lot :) I'm trying out the value '300'... just to be sure...
> better mileage, at least until your machine gets so heavily loaded that a
> simple admin request takes ten full minutes to process ;)
with the earlier versions of MM, first I used exim and that made the load
way to high (around 60) and often made it impossible to use... after I
started using postfix, things went much better.
> I'm not sure what the Right Fix is, however. MailList.MailList does not have
I'll let you know how it works out after changing the lock timeout...