Changes between Version 9 and Version 10 of Mutex


Ignore:
Timestamp:
May 23, 2008, 8:07:33 PM (9 years ago)
Author:
omry
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Mutex

    v9 v10  
    11== Mutex check failed ==
    2 Some of the operations !FireStats performs need to be synchronized to protect data integrity.
    3 
    4 !FireStats used the '''flock''' PHP function to perform this operation, but it does not work correctly on some servers.
    5 
    6 If your Mutex test fails, you can either try to upgrade your PHP, or tell FireStats not to synchronize those operations.
     2Some of the operations !FireStats performs need to be synchronized to protect data integrity.[[BR]]
     3!FireStats used the '''flock''' PHP function to perform this operation, but it does not work correctly on some servers.[[BR]]
     4If your Mutex test fails, you can either try to upgrade your PHP, or tell FireStats not to synchronize those operations.[[BR]]
     5Note: if the error you are seeing is "'''Managed to lock file, but should have failed for the test to succeed'''", try to ignore it and see if FireStats works. if you see problems disable the mutex.
    76
    87This is generally not recommended, but may be the only option for some users.
    98
    10 Note: if the error you are seeing is "Managed to lock file, but should have failed for the test to succeed", try to ignore it and see if FireStats works. if you see problems disable the mutex.
    119
    1210To disable synchronization, you need to uncomment the line