Comment 4 for bug 1694966

> any comments?

I hesitate a bit with a less than guaranteed safe fix. I was only thinking to add "assert(clientQlock)". There are a few similar cases where certain functions can't be called too early, so I'm not sure I see a value in allowing this one.

Practically, I suspect your patch will work well enough, so go ahead. It might be worth making a properly safe version >=3.15 using the read/write barriers in epicsAtomic.h if only to see that these are actually sufficient.