[Mailman-Users] Strange locking logs

[Michael Fischer v. Mollard]

Hi!

I faced a couple of entry in log/locks, so I decided to turn 
LIST_LOCK_DEBUGGING on. I got entry like:

Feb 05 14:53:03 2004 (18281) XXX.lock laying claim
Feb 05 14:53:03 2004 (18281)   File 
"/opt/local/mailman-2.1/scripts/driver", line 223, in ?
Feb 05 14:53:03 2004 (18281)     run_main()
Feb 05 14:53:03 2004 (18281)   File 
"/opt/local/mailman-2.1/scripts/driver", line 87, in run_main
Feb 05 14:53:03 2004 (18281)     main()
Feb 05 14:53:03 2004 (18281)   File 
"/opt/local/mailman-2.1/Mailman/Cgi/subscribe.py", line 91, in main
Feb 05 14:53:03 2004 (18281)     mlist.Lock()
Feb 05 14:53:03 2004 (18281)   File 
"/opt/local/mailman-2.1/Mailman/MailList.py", line 159, in Lock
Feb 05 14:53:03 2004 (18281)     self.__lock.lock(timeout)
Feb 05 14:53:03 2004 (18281)   File 
"/opt/local/mailman-2.1/Mailman/LockFile.py", line 249, in lock
Feb 05 14:53:03 2004 (18281)     self.__writelog('laying claim')
Feb 05 14:53:03 2004 (18281)   File 
"/opt/local/mailman-2.1/Mailman/LockFile.py", line 416, in __writelog
Feb 05 14:53:03 2004 (18281)     traceback.print_stack(file=logf)
Feb 05 14:53:04 2004 (18281) XXX.lock got the lock
Feb 05 14:53:04 2004 (18281)   File 
"/opt/local/mailman-2.1/scripts/driver", line 223, in ?
Feb 05 14:53:04 2004 (18281)     run_main()
Feb 05 14:53:04 2004 (18281)   File 
"/opt/local/mailman-2.1/scripts/driver", line 87, in run_main
Feb 05 14:53:04 2004 (18281)     main()
Feb 05 14:53:04 2004 (18281)   File 
"/opt/local/mailman-2.1/Mailman/Cgi/subscribe.py", line 91, in main
Feb 05 14:53:04 2004 (18281)     mlist.Lock()
Feb 05 14:53:04 2004 (18281)   File 
"/opt/local/mailman-2.1/Mailman/MailList.py", line 159, in Lock
Feb 05 14:53:04 2004 (18281)     self.__lock.lock(timeout)
Feb 05 14:53:04 2004 (18281)   File 
"/opt/local/mailman-2.1/Mailman/LockFile.py", line 260, in lock
Feb 05 14:53:04 2004 (18281)     self.__writelog('got the lock')
Feb 05 14:53:04 2004 (18281)   File 
"/opt/local/mailman-2.1/Mailman/LockFile.py", line 416, in __writelog
Feb 05 14:53:04 2004 (18281)     traceback.print_stack(file=logf)
Feb 05 14:53:04 2004 (18281) XXX.lock unlocked
Feb 05 14:53:04 2004 (3982) XXX.lock lifetime has expired, breaking

This seems strange to me. Any hints?

Thanks
	Michael

-- 
Michael Fischer v. Mollard, Netzwerkadministration
Heise Zeitschriften Verlag GmbH & Co KG
Helstorfer Straße 7
D-30625 Hannover
Tel: +49 511 5352 477; Email: Michael.Fischer.von.Mollard at heise.de