Romain Quetiez
|
8451ffdfb4
|
Regression introduced with the implementation of obsolescence: first install not working (Access denied for user ''@localhost)
SVN:trunk[4771]
|
2017-06-27 13:58:38 +00:00 |
|
Denis Flaven
|
61e2f97d6c
|
#1150: Spurious message "A restore is running..." - FIXED !
SVN:trunk[3864]
|
2016-01-20 15:56:09 +00:00 |
|
Romain Quetiez
|
8b45928d11
|
Instrumented the code to help in solving the "restore runing" issue. Completion of commits [3733] znd [3595] = issue an exception if something is going wrong within iTopMutex::TryLock (exceptions are correctly handled in the various places where TryLock is invoked)
SVN:trunk[3736]
|
2015-09-09 09:23:54 +00:00 |
|
Denis Flaven
|
586ec4515d
|
Mutex instrumentation for troubleshooting...
SVN:trunk[3595]
|
2015-06-19 14:46:08 +00:00 |
|
Denis Flaven
|
1aa489890c
|
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.
SVN:trunk[3591]
|
2015-06-12 17:00:41 +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 |
|