Re: GLASS

> Am 2012-03-29 um 00:27 schrieb Craig Latta:
> it might be a firewalling issue:
> gemstone chooses a random port or talking to its gems, in this case
> your pharo tools.
> With a restrictive firewall, probably only the “initiation” port
> (50378) is allowed.
> For best security, you should check that:
>  $grep  netldi services
> outputs
>  gs64ldi         50378/tcp        # Gemstone netldi
>
> and in
> /etc/init.d/gemstone (if you are following nicks template)
> that
> # Start GemStone
> startGemStone() {
>        logger "Starting GemStone server: "
>        daemon --user=$RUNASUSER $GEMSTONE_BIN/startGemstone
>        daemon --user=$RUNASUSER $GEMSTONE_BIN/startnet
>        success $" GemStone server startup"
>        echo
> }
>
> actually is
>
> # Start GemStone
> startGemStone() {
>        logger "Starting GemStone server: "
>        daemon --user=$RUNASUSER $GEMSTONE_BIN/startnet
>        daemon --user=$RUNASUSER $GEMSTONE_BIN/startGemstone
>        success $" GemStone server startup"
>        echo
> }
>
> (net before gemstone)
>
> also, check $GEMSTONE_BIN/startnet :
> the
> $GEMSTONE/bin/startnetldi -g -a $USER -n -l $GEMSTONE_LOGDIR/gs64ldi.log
> can be changed to
> $GEMSTONE/bin/startnetldi -g -a $USER -p 50377:50377 -n -l $GEMSTONE_LOGDIR/gs64ldi.log
>
> forcing netldi to only use one, your specified port.
>
>

>
> in my email, at the end I wrote about '-p 50377:50377'
> but according to James Foster of GemStone http://programminggems.wordpress.com/2008/09/25/slice-5/
> it should be -p 50378:50378 if you want to restrict the netldi to
> one port.
>
> However, the more i contemplate about the errormessage you
> gave me, I suspect the wrong ordering of
> startGemstone and startnet.
>
> try it by hand!
> source the def-file:
> $ . $GEMSTONE/seaside/defSeaside
> $ startnet
> $ startGemstone