Hi All-- Barry Warsaw wrote: > > The only thing I would add is that the default lock lifetime is 15 > seconds, so it's possible some other process would have broken the lock > during that time. That you didn't get an exception when you exited (and > thus unlocked) the list is a good sign that didn't happen. ;) >
Urk. I must live right. > Given the MailList object, there's no easy way to extend the lock's > lifetime. You can hack the LockFile.py file, or do something like: > > >>> m._MailList__lock.refresh(60 * minute) > Good to know; I'll add that to the FAQ when I can. >> I'm actually willing to live with these, unless they're damaging the >> archives somehow. Any guesses as to how difficult it would be to fix >> these by say, simply editing the .mbox and re-running arch --wipe? > > Unsure. What does bin/cleanarch -n say? > $ cleanarch -n <guppies.mbox 43413 messages found $ I was a little off. Metta, Ivan -- Ivan Van Laningham God N Locomotive Works http://www.pauahtun.org/ http://www.python.org/workshops/1998-11/proceedings/papers/laningham/laningham.html Army Signal Corps: Cu Chi, Class of '70 Author: Teach Yourself Python in 24 Hours ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
