On Wed, Sep 7, 2011 at 11:27 PM, Sven Van Caekenberghe <sven@beta9.be> wrote:

On 07 Sep 2011, at 21:32, laurent laffont wrote:

> On SmallHarbour we use a modified VM (only SecurityPlugin - https://gitorious.org/~laurentlaffont/cogvm/smallharbour ) ��so an image can open only a given set of ports. Each image / account has an allocated port number, so when an image starts a .st file is given as argument which stop all seaside adaptors and then start Zinc Seaside adaptor on a given port.
>
> The problem is: if I have saved a image with a socket opened on port XX, then try to start it on SmallHarbour on port YY - given that XX is forbidden - image crashes.

Apart from the fact that I think we have a serious problem here, see

http://code.google.com/p/pharo/issues/detail?id=4768

(but nobody seems to care, no one even confirmed that this happens for them too)

Now I care :) As we use a modified VM I'll try to make it reproduceable easily. I will tell you. (Anyway on SmallHarbour server itself it's easy. If you want access .....)

��

the workaround is (as I said to Lukas, and as I do myself) not to save images with a running server and just start the adaptor in a startup .st file.

Yes but for Pier this is a problem as the image is autosaved so when you restart it through SmallHarbour web interface ��there's a running server.��

Laurent.

��

HTH,

Sven