Smalltalk › Squeak › Squeak - Dev

[squeak-dev] WAKom startup on image restart

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

Brian Brown-4

[squeak-dev] WAKom startup on image restart

Hello all,

I'm running squeak headless as a seaside server on FreeBSD 6.2-RELEASE
and the vm version is:

squeak -version
3.9-8 #5 Tue Oct 10 19:50:54 PDT 2006 gcc 3.4.4
Squeak3.9alpha of 4 July 2005 [latest update: #7021]
FreeBSD freebsd.piumarta.com 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun
May 7 04:32:43 UTC 2006
[hidden email]:/usr/obj/usr/src/sys/GENERIC i386
default plugin location: /usr/local/lib/squeak/3.9-8/*.so

I have REPLServer running in the image, and WAKom - WAKom just won't
restart after the image is brought up. I have checked to make sure it
was in the startup list and I even moved it the end, but that doesn't
have any effect.

If I connect with REPLServer, I can run WAKom startOn: <whatever port>
and it works and serves fine.

Does anyone have any thoughts as to why this might be occurring?

thanks!

Brian

Igor Stasenko

Re: [squeak-dev] WAKom startup on image restart

2008/4/22 Brian Brown <[hidden email]>:

> Hello all,
>
> I'm running squeak headless as a seaside server on FreeBSD 6.2-RELEASE
> and the vm version is:
>
> squeak -version
> 3.9-8 #5 Tue Oct 10 19:50:54 PDT 2006 gcc 3.4.4
> Squeak3.9alpha of 4 July 2005 [latest update: #7021]
> FreeBSD freebsd.piumarta.com 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun
> May 7 04:32:43 UTC 2006
> [hidden email]:/usr/obj/usr/src/sys/GENERIC i386
> default plugin location: /usr/local/lib/squeak/3.9-8/*.so
>
>
> I have REPLServer running in the image, and WAKom - WAKom just won't
> restart after the image is brought up. I have checked to make sure it
> was in the startup list and I even moved it the end, but that doesn't
> have any effect.
>
> If I connect with REPLServer, I can run WAKom startOn: <whatever port>
> and it works and serves fine.
>
> Does anyone have any thoughts as to why this might be occurring?
>

Can it be the issue with socket reuse option? A system can hold a
socket for a while, even after process which opens it quit.
So, after starting another one, it can't bind to same port for some
period of time unless you set SO_REUSEADDR in socket options.

> thanks!
>
> Brian
>
>

--
Best regards,
Igor Stasenko AKA sig.

Ramon Leon-5

RE: [squeak-dev] WAKom startup on image restart

In reply to this post by Brian Brown-4

> Hello all,
>
> I'm running squeak headless as a seaside server on FreeBSD
> 6.2-RELEASE and the vm version is:
>
> squeak -version
> 3.9-8 #5 Tue Oct 10 19:50:54 PDT 2006 gcc 3.4.4
> Squeak3.9alpha of 4 July 2005 [latest update: #7021] FreeBSD
> freebsd.piumarta.com 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun
> May 7 04:32:43 UTC 2006
> [hidden email]:/usr/obj/usr/src/sys/GENERIC i386
> default plugin location: /usr/local/lib/squeak/3.9-8/*.so
>
>
> I have REPLServer running in the image, and WAKom - WAKom
> just won't restart after the image is brought up. I have
> checked to make sure it was in the startup list and I even
> moved it the end, but that doesn't have any effect.
>
> If I connect with REPLServer, I can run WAKom startOn:
> <whatever port> and it works and serves fine.
>
> Does anyone have any thoughts as to why this might be occurring?
>
> thanks!
>
> Brian
>

Why aren't you just starting it with the port you want, don't rely on what's
in the image, force what you want?

squeakvm -mmap 100m -headless -vm-sound-null -vm-display-null app.image ""
port 3000

Ramon Leon
http://onsmalltalk.com

Brian Brown-4

Re: [squeak-dev] WAKom startup on image restart

In reply to this post by Igor Stasenko

On Tue, Apr 22, 2008 at 1:14 PM, Igor Stasenko <[hidden email]> wrote:
> 2008/4/22 Brian Brown <[hidden email]>:

> Can it be the issue with socket reuse option? A system can hold a
> socket for a while, even after process which opens it quit.
> So, after starting another one, it can't bind to same port for some
> period of time unless you set SO_REUSEADDR in socket options.
>

If that was the issue, I suspect I could not connect and immediately
issue WAKom start and have it work....

>
> > thanks!
> >
> > Brian
> >
> >
>
>
>
> --
> Best regards,
> Igor Stasenko AKA sig.
>
>

Brian Brown-4

Re: [squeak-dev] WAKom startup on image restart

In reply to this post by Ramon Leon-5

On Tue, Apr 22, 2008 at 1:19 PM, Ramon Leon <[hidden email]> wrote:
>
> >
>
> Why aren't you just starting it with the port you want, don't rely on what's
> in the image, force what you want?
>
> squeakvm -mmap 100m -headless -vm-sound-null -vm-display-null app.image ""
> port 3000

If WAKom doesn't start, I don't thing the port parameter will have any
effect, will it?

>
> Ramon Leon
> http://onsmalltalk.com
>
>
>

Ramon Leon-5

RE: [squeak-dev] WAKom startup on image restart

> > Why aren't you just starting it with the port you want,
> don't rely on
> > what's in the image, force what you want?
> >
> > squeakvm -mmap 100m -headless -vm-sound-null
> -vm-display-null app.image ""
> > port 3000
>
> If WAKom doesn't start, I don't thing the port parameter will
> have any effect, will it?

The port parameter should force it to start, quicker to see than to discuss.

Ramon Leon
http://onsmalltalk.com