Am 08.12.2011 um 11:32 schrieb Sven Van Caekenberghe:
On 08 Dec 2011, at 11:20, Norbert Hartl wrote:
I didn't get that Javier meant the same as Eliot. What should be done is pretty clear to me after dealing 20 years with unix ;) But thank you very much for explaining. I didn't know about the -s switch in kill. I always just do kill -USR1 ...
I was thinking you were one of those Windows guys ;-)
shame on you ;)
What he meant was: are there any threads doing anything unusual (as compared to a clean image). But of course, if this was a busy server, there would of course be many threads and sockets open.
The image wasn't that busy. But I need some time to investigate what is normal in an image before I can judge about oddities in my other images.
Anyway: this issue was, as you probably read, that you lost a semaphore every time you saved the image, since you do that every hourâ¦
But that won't help in recovering the image.
I lost all the data but the data wasn't that important. Dealing my whole time with GemStone I ran out of the habit to take extra measures to keep my data. So from now on I'm a Fuel user. I just write out the data using fuel before saving an image so it is easy to reconstruct. My quick take on journaling with manual replay :) Trying to recover the image was not important for me but for pharo. I just liked to participate in solving a problem that is hard to debug. thanks, Norbert