[Pharo-project] End of startup script behavior
Guys, Maybe I missed this, but did something change with the behavior at the end of a startup script between 1.3 and 1.4 ? It used to be that the image kept on running unless you asked it to quit explicitly, now it seems that the image automatically quits unless you keep it busy. Can someone confirm this ? Was this intentional ? What would be the recommended way to keep the image open ? Somehow something like [ (Delay forDuration: 1 hour) wait ] repeat. seems so silly, but it works. Thx, Sven
Sven, Reminds me of one of early Dolphin hacks. OA being who they are, eventually fixed the snag. The problem was that event loop needed to be running for some late startup tasks to run properly. In this case, the image would do nothing vs. quit, but I suspect it's the same lesion under a different name. My fix was to queue a deferred action and then fork a thread to wait until after OA's startup, and then did the offending work. It worked, and they added more or less the same thing to Dolphin. Interestingly, I never had to remove my hack<g>, Please note (nobody wants to hear this) that Dolphin has thread synchronization objects, weak collections, and other nice things that make us look bad by comparison, even ignoring the calendar differences. Good luck! Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Sven Van Caekenberghe [sven@beta9.be] Sent: Tuesday, January 31, 2012 4:57 AM To: Pharo-project@lists.gforge.inria.fr Development Subject: [Pharo-project] End of startup script behavior Guys, Maybe I missed this, but did something change with the behavior at the end of a startup script between 1.3 and 1.4 ? It used to be that the image kept on running unless you asked it to quit explicitly, now it seems that the image automatically quits unless you keep it busy. Can someone confirm this ? Was this intentional ? What would be the recommended way to keep the image open ? Somehow something like [ (Delay forDuration: 1 hour) wait ] repeat. seems so silly, but it works. Thx, Sven
Are you sure that you do not have an error because it would kill it. I do not see what we change to get the behavior you mentioned. On Jan 31, 2012, at 10:57 AM, Sven Van Caekenberghe wrote:
Guys,
Maybe I missed this, but did something change with the behavior at the end of a startup script between 1.3 and 1.4 ?
It used to be that the image kept on running unless you asked it to quit explicitly, now it seems that the image automatically quits unless you keep it busy. Can someone confirm this ? Was this intentional ?
What would be the recommended way to keep the image open ?
Somehow something like
[ (Delay forDuration: 1 hour) wait ] repeat.
seems so silly, but it works.
Thx,
Sven
On 31 Jan 2012, at 11:50, Stéphane Ducasse wrote:
Are you sure that you do not have an error because it would kill it. I do not see what we change to get the behavior you mentioned.
Yes, I am sure. With 1.3 the startup script could be: ZnServer startDefaultOn: 8080 and the server would keep on running. With 1.4 the following script: NonInteractiveTranscript stout install. (ZnServer defaultOn: 8080) logToTranscript; start. Clearly shows the image quiting without errors: 2012-01-31 12:24:05 706209 I Starting ZnMultiThreadedServer HTTP port 8080 2012-01-31 12:24:05 835258 D Initializing server socket ----QUIT/NOSAVE----an Array(31 January 2012 12:24:05 pm) pharo-ws-server.image priorSource: 35443879 2012-01-31 12:24:05 706209 D Releasing server socket 2012-01-31 12:24:05 706209 I Stopped ZnMultiThreadedServer HTTP port 8080 Sven
participants (3)
-
Schwab,Wilhelm K -
Stéphane Ducasse -
Sven Van Caekenberghe