[Mailman-Users] Lock Files

[Mark Sapiro]

Justin Denick wrote:
>
>There are (3) 'currently'  lock files. They are for /bin/mailmanctl and the
>qrunners
>ArchRunner and OutgoingRunner.


The files 'master-qrunner' and 'master-qrunner.host.pid' are not list
locks. They are the lock that prevent starting mailmanctl when it's
already running.

Are there entries in Mailman's smtp-failure log?


Is there only one listname.lock file and two listname.lock.host.pid.seq
files? If so, one pid has the lock and the other is waiting.

Do the timestamps and other things about these lock files change over
time?

See
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.076.htp>.


>Also check Mailman's 'locks' log if there is one, and Mailman's 'error'
>
>
>
>Here's some output from the locks log
>
>Mar 27 17:00:33 2007 (32114)   File
>"/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 115, in _dispose
>Mar 27 17:00:33 2007 (32114)     mlist.Lock
>(timeout=mm_cfg.LIST_LOCK_TIMEOUT)
>Mar 27 17:00:33 2007 (32114)   File "/var/lib/mailman/Mailman/MailList.py",
>line 159, in Lock
>Mar 27 17:00:33 2007 (32114)     self.__lock.lock(timeout)
>Mar 27 17:00:33 2007 (32114)   File "/var/lib/mailman/Mailman/LockFile.py",
>line 260, in lock
>Mar 27 17:00:33 2007 (32114)     self.__writelog('got the lock')
>Mar 27 17:00:33 2007 (32114)   File "/var/lib/mailman/Mailman/LockFile.py",
>line 416, in __writelog
>Mar 27 17:00:33 2007 (32114)     traceback.print_stack(file=logf)


I'm not sure why the above trace is logged at all, but I don't think is
is significant.

-- 
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan