[TYPO3-core] RFC: Bug #7630: Locking Problems with TSFE->set_no_cache()

[Oliver Hader]

Hi,

Michael Stucki schrieb:
> Hi Olly & Jeff,
>> Thanks for your patch. The debug during development is fine, maybe we
>> can introduce a global configuration property to toggle this logging via
>> install tool / typo3conf/localconf.php?
> 
> Call t3lib_div::sysLog() and set severity to "info" (0). That should be
> complitely fine for things like this.
> 
> So can you please incorporate the sysLog() calls from Jeffs patch?
> 
>> What do you think?
> 
> Reviewed & tested, +1!

I've modified the post patch of #7333. It has the following modifications:
* adds a new method t3lib_lock::sysLog() which calls again 
t3lib_div:sysLog and prepends some common information, e.g.:
25-02-08 18:09 - cms: Locking 
[simple::0aeafd2a67a6bb8b9543fb9ea25ecbe2]: Acquired lock
25-02-08 18:09 - cms: Locking 
[simple::712fa1bc0bb5e4e6a491065c075cecd2]: Acquired lock
25-02-08 18:09 - cms: Locking 
[simple::0aeafd2a67a6bb8b9543fb9ea25ecbe2]: Released lock
25-02-08 18:09 - cms: Locking 
[simple::712fa1bc0bb5e4e6a491065c075cecd2]: Released lock

* added a new class variable $resource which is used for the filename of 
the lock or the semaphore resource
* changed to disposal of class variable $id to contain the hash which 
was used to create the locking resource (=identifier)
* added a check if typo3temp/locks/ directory exists and creates it

Please test and review this patch again. Thanks!

olly
-- 
Oliver Hader
http://inpublica.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0007630_v2.patch
Type: text/x-patch
Size: 7331 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20080225/814ec157/attachment.bin