Sig, Are we discussing the same OS? What you are describing matches my experience on Windows; on Linux, AFAIK, one can just stomp all over the files and leave a mess. Perhaps something has changed to make it safer since I last trashed an image that way. I agree that there are times when it does not matter, so any safety mechanism needs to be optional, or better yet tied to a development session vs. a deployed session. Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Igor Stasenko [siguctua@gmail.com] Sent: Wednesday, January 19, 2011 8:35 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Any Clue.. On 19 January 2011 14:14, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote:
Sig,
Please forgive me for being skeptical, but it is certainly worthy of a test on my end. How do the multiple processes coordinate access to the change log? Not having seen an IDE complain about access to either image or changes, and knowing that I have been bitten by this, I am not sure how to square it.
Access to single .changes file are handled by image, and i think it is handled well (it barks that .changes cannot be opened, if some other process already opened it). But that is a completely different story , because .image file are handled by vm itself, not by image.. From VM perspective, a .changes file are not mandatory in order to run your image, so why it should care about it?
Bill
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Igor Stasenko [siguctua@gmail.com] Sent: Wednesday, January 19, 2011 8:08 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Any Clue..
There is nothing wrong starting multiple processes using single .image file. During startup, vm just reads data from it. And when writing to an .image file, a process who first opens it should obtain a global lock on it, so nothing will have chances to interfere. So, it seems that image file was damaged or not written completely..
-- Best regards, Igor Stasenko AKA sig.