On Sep 7, 2011, at 9:32 PM, laurent laffont wrote:

> On Wed, Sep 7, 2011 at 9:04 PM, Sven Van Caekenberghe <sven@beta9.be> wrote:
> Hi Laurent,
>
> On 07 Sep 2011, at 20:24, laurent.laffont@gmail.com wrote:
>
> > here insert explanation of what you were doing, suspect changes you've
> > made and so forth.
>
>
> Haha I haven't seen the mail will go the list :) ��First time I use the mail out function.
>
> Anyway some explanations because this has corrupted my image.
>
> 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.

It would be good that it does not crash :)
do not mean crash or shutdown nicely.
I mean if you are not in headless does it crash?

Yes it crashes only in headless mode - the (not so?) funny thing is that daemontools restart it immediately, then crash, restart, crash, restart .... huge PharoDebug.log :)

With display the debugger pops up with the stack trace that was sent.

Laurent

��

>
>
> What were you doing ?
> Is this something reproduceable ?
>
> Yes.
>
>
> Is this in a standard 1.3 or did you somehow upgrade Zn to the latest version ?
>
> It's a 3 weeks old Pier 2 image from Lukas Jenkins server so I first want to get latest one and check if the problem is still here.
>
>
> Doing so might help (the primitive failed on close, flush is now swallowed).
>
>
> OK thanks.
>
> Laurent.
>
>
> Sven
>
>
>
>