[Glass] Netldi and /etc/services (was Newbie on GLASS - Hello world fail)

[Dale Henrichs via Glass]

Editing /etc/services is indeed the "approved" method for associating a 
netldi name with a specific port, but you do have to "figure this out 
ahead of time" and you have to use root to update /etc/services .... The 
drawback is that this needs to be done for every stone and a free port 
either needs to defined ahead of time (like 50377) or the /etc/services 
entry needs to be added after the netldi figures out which port is free ...

I intend to automate this and if folks are comfortable with having to 
enter their `sudo` password whenever a stone is created, then I can go 
this route ... if there are (good) reasons for not updating 
/etc/services on every stone creation, then I can come up with alternate 
schemes...

What do you guys think?

Dale

On 09/20/2015 09:52 PM, Jupiter Jones via Glass wrote:
>> 1- after installing via "./installServer devKit 3.2.8.1" netLDI listens in
>> different random ports each time it starts. How do I get it to listen on the
>> one in the default gs64ldi port 50377 always instead?
>>
>> In /etc/services file add the following line:
>> gs64ldi         50377/tcp        # Gemstone netldi
> To have the devKit_ldi netldi process use the same port each time, also add to /etc/services:
>
> devKit_ldi	50378/tcp		# DevKit GemStone Network Long Distance Information (LDI)
>
> I typically don’t need to add this entry in development - ie. dev and stone on the same machine. The only time I add this entry is when I want my local tODE to connect to a remote stone. I add the stoneName_ldi to both the local and remote /etc/services to ensure they both lookup the same port number
>
> cheers
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass