Hi Lukas, I'm using Pharo 1.1 + Cog (04/10/2010) + Seaside 3 and haven't that problem. I started Kom (WAKom startOn: 9090) once and when I open my image it start automatically all times. Facundo ps: I'm using Windows 7. On Tue, Oct 26, 2010 at 9:04 AM, Lukas Renggli <renggli@gmail.com> wrote:
Hi Eliot,
I noticed that on the Cog VM the Kom Seaside server does not automatically start to listen, even if there is a process waiting at the semaphore of the socket. Singaling that semaphore from the process browser fixes the problem and the Cog image is fully working until the next time it is opened.
The exact same image opened with an old VM does not show the problem and immediately starts to listen by itself.
Did anybody else notice the same problem? Anybody found a solution?
Lukas
-- Lukas Renggli www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project