[Glass] Stop a Gem running an endless FFI loop

[Bruno Buzzi Brassesco]

Dale,

Actually is a Smalltalk loop but each iteration calls a FFI function, that
maybe does or does NOT return.

regards,
bruno

El mié, 5 may 2021 a las 19:00, Dale Henrichs (<
dale.henrichs at gemtalksystems.com>) escribió:

> Bruno,
>
> Here's the response from engineering:
>   If you have hot loop in C code called from the FFI ,
>   you will have to  use either kill -TERM or kill -9 .
>
> We plan to talk over possible new features later this week ...
>
> Dale
>
> On May 5 2021, at 12:13 pm, Bruno Buzzi Brassesco via Glass <
> glass at lists.gemtalksystems.com> wrote:
>
> Hi,
> GS: 337
> Which is the best way to stop a Gem running an endless FFI loop ?
> Let's say Gem1 starts Gem2 that runs the FFI loop.
>
> The FFI Gem2 is started like (inside Gem1):
> s := GsExternalSession new.
> s username: 'xx'; password: 'xx'; login.
> s forkString: 'FFI endless loop here'.
>
> So far so good..
> But when i try to stop it with:
> System stopSession: s sessionId. (in Gem1)
> the command: netstat -lpn | grep 6060 - it shows the gem still running on
> that port. So Gem2 still running
> Gem2 only ends if I logout from Gem1.
>
> Also tried to use #forceLogout but sometime works fine but other answer
> the following error:
> 'session with stone session ID of 127 still present 20 seconds after
> logout'
>
> And last question is:
> Which is the difference between GsExternalSessio>>sessionId and
> GsExternalSession>>stoneSessionId ?
>
> Right now the kill is done with:
> System performOnServer: 'kill -9 ' , s gemProcessId printString
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> https://lists.gemtalksystems.com/mailman/listinfo/glass
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gemtalksystems.com/mailman/private/glass/attachments/20210505/591c9f1b/attachment.htm>