[TYPO3-core] RFC: #8980: unlink of non existant lockfiles generates warnings in frontend

[André Stösel]

> Maybe we should check the lockfiles ctime if we can't aquire the lock
> in order to detect stale lock files. Of course this adds another
> race possibilty if two processes try to remove the stale lock at the
> same time, but in this case we can safely ignore any errors of the
> unlink() call (IOW use @unlink). I think if the files ctime is older
> than 120 seconds it is safe to assume that it is a stale lockfile.
> 
> Anyway the fopen(..., "x") prevents the possibility that two (or more)
> processes aquire the same lock at the same time, so I really think its
> worth it.

Patch with check for stale lockfile attached.
So, are there still any issues?
I'd love to see this patch in the next version ;)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 8980_v4.diff
Type: text/x-patch
Size: 1420 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20100922/5302f7b8/attachment.bin>