VM freeze and crash when saving
David T. Lewis
lewis at mail.msen.com
Wed Apr 18 15:43:07 UTC 2007
Sorry that I was right :(
On Wed, Apr 18, 2007 at 04:16:11PM +0200, Florian Minjat wrote:
> David T. Lewis wrote:
> >I think that the problem with #forkSqueak will come back again.
> >It was probably caused by some restriction on the ISP server.
> >For example, when your production image gets very large, you may
> >find that the #forkSqueak no longer works (I am only guessing
> >of course). For this reason, I suggest you have some kind of
> >log file to keep track of whether the backups succeed. You
> >could have the background Squeak (the one doing the actual
> >save) write something to a log file when it is done, or you
> >can have the foreground Squeak check the status of the
> >background Squeak (#succeeded or #isComplete) to see if it
> >ran successfully. Also you know that if the background
> >Squeak has a pid of -1, then the fork must have failed, so
> >can watch for that specific problem.
> You was right. The fork worked four times and then always returned -1.
> The image is not so large (50Mo). But as my virtual server does not
> have that much ram (128Mo), the os doesn't like the allocation of a
> new one...
> So this method is not secured at all.
> I need to find something else...
More information about the Squeak-dev