On Fri, 26 Oct 2012 18:12:07 +0100 "Mike Cowlishaw" <[email protected]> wrote:
> > > > Curious .. I use mutex in Rexx (mostly to protect .ini file > > > updates in > > > Windows and Linux, mostly Windows) and have had occasional > > > failures that appeared to be due to some kind of corruption. > > > Could this problem be related ... i.e., mutexes not working as > > > expected? > > > > > > > If you mean by corruption that your ini file was corrupted > > then I would say this is related. At least when this is > > Linux. I cannot speak for Windows as I do not use Windows. > > > > Currently, if e.g. you call SysCreateMutexSem() from > > different scripts for the same semaphore then you would > > expect the second invocation of > > SysCreateMutexSem() to fail. But it doesn't. This could cause > > havoc to your inifile. > > OK, just skimmed the code -- I'm only using SysCreateMutexSem() once > (on startup -- I hope, will double-check that tomorrow) .. the number > returned from that is then used in multiple threads at a later time. > Which is as intended, I think. > If you call SysCreateMutexSem() only once then you are at least not affected by the problems we are discussing today. Apparently you do not call SysOpenMutexSem() because then you would get a segmentation fault when using the returned handle in a subsequent call to a mutex function. -- Manfred ------------------------------------------------------------------------------ The Windows 8 Center In partnership with Sourceforge Your idea - your app - 30 days. Get started! http://windows8center.sourceforge.net/ what-html-developers-need-to-know-about-coding-windows-8-metro-style-apps/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
