Thanks for the suggestion. It is probably the case.

Le 17/7/16 �� 23:27, Nicolai Hess a ��crit��:

Hi Valentin, Ithink you can not print to stdout during shutdown and restart.
It will end in a Loop of writing to stdout, throwing an exceptions because it can not write and trying to log the error on stdout, throwing an error...

Am 17.07.2016 18:36 schrieb "Valentin Ryckewaert" <valentin.ryckewaert@gmail.com>:

i will do it tomorrow.

2016-07-17 17:23 GMT+02:00 stepharo <stepharo@free.fr>:

did you try to solution proposed?

Stef

Le 17/7/16 �� 16:22, Valentin Ryckewaert a ��crit��:

Hello Stef,

no i'm still on it :(

I'm going to test every code I modified��

Valentin

2016-07-17 15:23 GMT+02:00 stepharo <stepharo@free.fr>:

HI valentin

did you solve your problem?

Stef

Le 12/7/16 �� 15:33, Valentin Ryckewaert a ��crit��:

Hello everyone,

I'm currently working on the project file policy and I'm having a problem that I don't understand

I import my code, configure my image as readOnly (Pharo won't try to write on changesFiles,source,image....), set the folder of the image in readonly and try to open the image again and it's not possible, I don't get any stacktrace so it's hard to understand the problem.

PS : If we set back the folder in write mode, it's possible again to open the image again.

Here is the code to reproduce the bug, could someone give me a clue please?

sudo rm -r testPharo

mkdir testPharo

cd testPharo

echo "Metacello new��

smalltalkhubUser: 'Uryon' project: 'Coral';

configuration: 'Coral';

version: #development;

onConflictUseIncoming;

load.

SmalltalkImage configureSystemAsReadonlyAndQuit:true

" >> load.st

mkdir coral

cd coral

curl get.pharo.org/alpha | bash��

curl get.pharo.org/vm60 | bash��

pharo-vm/pharo Pharo.image ../load.st��

cd ..

chmod -R -w coral

coral/pharo-vm/pharo coral/Pharo.image