Hello Dick, > -----Original Message----- > From: Dick Porter [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 26, 2003 3:28 PM > > > > If the shared memory is corrupted, the runtime reverts to a non-shared > setup. This has the side effect of preventing process forking. > > You can delete the shared memory files in ~/.wapi when this > happens, but > it would be very useful if you could track down _why_ the corruption > occurred. Running out of space might do it, but the sanity > check looks > at the first few bytes. >
We have this behaviour on one (and only one) of our machines. We were not been able to track this issue down yet. Could this be a race condition between two processes? We are starting multiple instances of one Mono app from another multithreaded Mono app. Jörg. _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
