Breaking expired locks logs a traceback
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Mailman |
New
|
Medium
|
Unassigned |
Bug Description
This looks like a bug to me, though perhaps there's
some reason a traceback is needed each time an expired
lock is broken?
Jun 29 23:51:18 2005 (4405) bryans-list.lock lifetime
has expired, breaking
Jun 29 23:51:18 2005 (4405) File
"/usr/local/
Jun 29 23:51:18 2005 (4405) main()
Jun 29 23:51:18 2005 (4405) File
"/usr/local/
Jun 29 23:51:18 2005 (4405) qrunner.run()
Jun 29 23:51:18 2005 (4405) File
"/usr/local/
in run
Jun 29 23:51:18 2005 (4405) filecnt = self._oneloop()
Jun 29 23:51:18 2005 (4405) File
"/usr/local/
in _oneloop
Jun 29 23:51:18 2005 (4405) self._onefile(msg, msgdata)
Jun 29 23:51:18 2005 (4405) File
"/usr/local/
in _onefile
Jun 29 23:51:18 2005 (4405) keepqueued =
self._dispose(
Jun 29 23:51:18 2005 (4405) File
"/usr/local/
line 38, in _dispose
Jun 29 23:51:18 2005 (4405) return
IncomingRunner.
Jun 29 23:51:18 2005 (4405) File
"/usr/local/
line 115, in _dispose
Jun 29 23:51:18 2005 (4405)
mlist.Lock(
Jun 29 23:51:18 2005 (4405) File
"/usr/local/
Jun 29 23:51:18 2005 (4405) self.__
Jun 29 23:51:18 2005 (4405) File
"/usr/local/
Jun 29 23:51:18 2005 (4405) important=True)
Jun 29 23:51:18 2005 (4405) File
"/usr/local/
__writelog
Jun 29 23:51:18 2005 (4405)
traceback.
Thanks,
Bryan
[http://
Oh, I'm running 2.1.6.