[Mailman-Developers] Faulty Member Subscribe/Unsubscribes

[Andrew Case]

Mark,

Another question below...

>> I'm suspicious there may be a locking issue and config.pck is reverting
>> to
>> config.pck.last.  I found this thread rather helpful in analyzing
>> potential problems, but I have yet to figure anything out:
>>   http://web.archiveorange.com/archive/v/IezAOgEQf7xEYCSEJTbD
>
>
> The thread you point to above is relevant, but it is not a locking
> issue. The problem is due to list caching in Mailman/Queue/Runner.py
> and/or nearly concurrent processes which first load the list unlocked
> and later lock it. The issue is that the resolution of the config.pck
> timestamp is 1 second, and if a process has a list object and that list
> object is updated by another process within the same second as the
> timestamp on the first process's object, the first process won't load
> the updated list when it locks it. This can result in things like a
> subscribe being done and logged and then silently reversed.

You think it should be okay though if my qrunners are all running on my
mta server instead of my webserver though.  This wouldn't be causing a
problem with the caching right?

Thanks,

--
Drew