Comment 2 for bug 541291

I see that this occurs when the lock was released in the middle of switching the channel from a search timer to a TCP circuit, but due to changes in the timer library some time back we no longer need to release the lock when calling epicsTimer::start if we also hold this same lock in the timer expire callback. This is necessary when calling epicsTimer::cancel(), but epicsTimer::start no longer calls epicsTimer::cancel().

edited on: 2006-05-22 18:33