5 Commits

Author	SHA1	Message	Date
steffen123	e9346f6b82	make it record source of lock holding, print if required ... this is mostly intended for devs	2010-07-10 20:10:04 +02:00
fpdb-mme	f5d2f5a2dc	fix: according to doctests os_independend_kill() is supposed to return None	2009-11-01 09:58:14 +01:00
fpdb-mme	6fcf81e566	bugfix: InterProcessLock.locked() was broken cause InterProcessLock.aquire() no longer raises SingleInstanceError ... - fixed InterProcessLock.locked() - fixed doctests notes: - doctests run ok on linux with InterProcessLockFcntl and InterprocessLockSocket - doctests fail on linux/wine with InterprocessLockWin32 when trying to aquire the lock held by the process created on the fly. just a guess ..maybe the mutex is not released automatically when terminating the process. does native win32 guarantee this?	2009-11-01 09:51:00 +01:00
Eric Blade	bfec6916f6	trying to get my new install of git to freaking work	2009-08-12 04:09:04 -05:00
sqlcoder	fb4ad79803	use someone else's interprocess locking code instead of python locks/semaphores - needs testing in Linux	2009-07-19 12:28:17 +01:00