[Mailman-Users] run away process - cannot flock

[Paul H Byerly]

      Twice now my CPU has pegged after a message went through 
Mailman.  Top shows a python2.2 process belonging to Mailman.  Shutting 
Mailman  down stops it, but it comes right back when Mailman is 
restarted.  Killing the process ends the problem.
      In digging through the logs I found similar entries in 
mailmn/logs/smtp-failure:

Jul 17 23:06:57 2003 (2643) delivery to foo at gloryworks.com failed with code 
451: 4.0.0 cannot flock(/etc/mail/access.db, fd=7, type=1, 
omode=37777777777, euid=0): No locks available

Jul 18 22:30:49 2003 (22481) delivery to foo2 at cookteam.com failed with code 
451: 4.0.0 cannot flock(/etc/mail/access.db, fd=7, type=1, 
omode=37777777777, euid=0): No locks available

      As this is the only two times I have such an entry and each proceeds 
the runaway process to the minute, I assume it's related.  Google produced 
nothing that enlightened me.

Mailman 2.1.2
Redhat 7.1
Python 2.2.2

TIA, Paul