On Fri, 26 Oct 2012 08:49:09 -0500 David Ashley <[email protected]> wrote:
> I disagree with this assessment. I believe the second call to > SysVreateMutexSem should fail because the semaphore already exists. > The second script should be using SysOpenMutexSem to get access to the > existing semaphore. > Perhaps I wasn't clear with my statements. Actually, you agree with me. I also believe that the second call to SysCreateMutexSem() should fail. I had removed sem_unlink in SysCreateMutexSem(), rebuild ooRexx from source, and then it worked as expected. The 2nd call to SysCreateMutexSem() failed and SysOpenMutexSem() succeeded. Then I got a segmentation fault which is the other thread I opened. > I believe that the Windows version of this would cause the second > script to fail because the semaphore already exists. > > Mark, Rick - please try this out on Windows and let me know if I am > correct. > > If I am correct the fix should be to remove the sem_unlink() call in > the *nix version of Rexxutil. > Exactly! -- Thanks, Manfred ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
