Denis Flaven
|
95d6b640b1
|
#1150: Spurious message "A restore is running..." - FIXED !
SVN:2.1.0[3867]
|
2016-01-20 16:08:12 +00:00 |
|
Romain Quetiez
|
86e6c8295f
|
Instrumented the code to help in solving the "restore runing" issue. Retrofit from trunk of [3733] and [3595]: better error handling... check error.log!
SVN:2.1.0[3738]
|
2015-09-09 09:44:39 +00:00 |
|
Denis Flaven
|
706e6c56ff
|
Mutex instrumentation for troubleshooting...
SVN:2.1.0[3596]
|
2015-06-19 14:48:13 +00:00 |
|
Romain Quetiez
|
1804903ee4
|
Make sure that the SQL mutexes are specific to the current iTop instance, but still preserving the capability for the setup to detect an already running cron job with or without a valid config file -reintegrated from trunk
SVN:2.1.0[3592]
|
2015-06-15 09:55:31 +00:00 |
|
Romain Quetiez
|
1ba2ed809c
|
Added a warning when upgrading the application while a CRON is being executed on the same DB
SVN:trunk[3239]
|
2014-07-03 07:11:43 +00:00 |
|
Denis Flaven
|
a72e15023f
|
Proper handling of the re-entrence of the Lock/Unlock within the same PHP page. Previously the code was sometimes performing 2 Unlock() for each Lock().
SVN:trunk[3217]
|
2014-06-18 15:24:31 +00:00 |
|
Denis Flaven
|
ce9806b01c
|
Allow re-entrance in the same named mutex within the same PHP page.
SVN:trunk[3115]
|
2014-04-01 09:50:21 +00:00 |
|
Romain Quetiez
|
abae2129ad
|
CRON: protection against re-entrance now relies on a bullet-proof mutex. Also added the option 'debug=1' to output the call stack in case an exception occurs (not always because of passwords being shown in the call stack)
SVN:trunk[2834]
|
2013-08-26 15:29:32 +00:00 |
|