[Mailman-Developers] URGENT Please Help: Duplicates with 2.0 final

[Todd Joseph]

BW>Are you running Mailman on an NFS mounted file system?  Locking
BW>/shouldn't/ be susceptible to NFS issues, but it still isn't a
BW>terribly good idea.

No -- all local filesystems.

BW>Another scenario is that you've cranked up your qrunner process
BW>limits, but not appropriatedly adjusted your qrunner lock lifetime.
BW>In that case, qrunner could be running for a long time, exceeding the
BW>lock lifetime, and allowing a future cron started qrunner to break the
BW>still running qrunner's lock.

Interesting.  I haven't adjusted any of this intentionally. 

BW>The best way to see if this is happening is to edit cron/qrunner
BW>around about line 274, where the LockFile instance is created.  Add an
BW>argument "withlogging=1" to turn on lock file logging.  Then you'd
BW>study the log to see if you get any "lock broken" messages.

OK, I'll try that. 

BW>    TJ> OK, I'm bad.  I changed them in the Defaults.py file.  I tried
BW>    TJ> to use the mm_cfg.py file, but ran into a problem (was a few
BW>    TJ> months ago, don't remember what exactly happened).
BW>
BW>I'd like to know about those, since changing mm_cfg.py is better.
BW>Otherwise future upgrades could overwrite your changes.

I'll letcha know. 

Thanks for all the help.

Todd