>>But currently we are at the stage that the SSLMutex passes a NULL >>filename in for the mutexname and assumes the apr will generate >>"something". >It's more correct to say that it assumes APR "does the right thing", which >it does. Under Win32 it creates an unnamed mutex ala the mpm. The creation is OK so far.
But the problem occurs when the child trys to open this mutex. Since it hasn't access the the win32 handle created by the parent, it trys to open a unnamed mutex, which of course won't do it. André
