Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add netldi magic line into autogenerated .topazini #161

Closed
marianopeck opened this issue Jan 27, 2017 · 9 comments
Closed

Add netldi magic line into autogenerated .topazini #161

marianopeck opened this issue Jan 27, 2017 · 9 comments

Comments

@marianopeck
Copy link
Contributor

In order to connect from topaz with RPC we need the netldi magic line in the .topazini. It would be nice if GsDevKit_home can add that in the auto-generated .topazini:

startTopaz myStone_333 -r -I $GS_HOME/server/stones/lucidiaLLC_333/.topazini

And in topaz.ini add:

set gemnetid !tcp@localhost#netldi:40600#task!gemnetobject

@dalehenrich
Copy link
Member

startTopaz already uses -I to pick up the .topazini, but yes, the gemnetid line needs to be added ... I'll look into that right now ... while the iron is hot:)

@dalehenrich
Copy link
Member

@marianopeck here's a sample .topazini:

SET GEMSTONE test_333
set user DataCurator
set password swordfish
set gemnetid !tcp@foos#netldi:test_333_ldi#task!gemnetobject

Note that I'm using the name of the netldi: test_333_ldi not the port number. At the time the .topazini is generated a netldi port number is not known ... A port number is really only needed if you are using topaz for remote logins and you have nut associated the netldi name with a port number in /etc/services ... on the local host the netldi name is fine ...

What do you think?

dalehenrich added a commit that referenced this issue Jan 27, 2017
…eateStone. The gemnetid specifies the name of the netldi to use when logging in. Makes it unnecessary to use `-l` whenever running `startTopaz`
@dalehenrich
Copy link
Member

Tested things locally and they work ... also added a symlink from $GS_HOME/server/stones/<stone-name>/tode to $GS_HOME/sys/local/server/stones/<stone-name> ... more than once I've wanted to see what tODE scripts were available when sitting the $GS_HOME/server/stones directory and vowed to add the link ... today I remembered my vow ... hot irons and all that:)

dalehenrich added a commit that referenced this issue Jan 27, 2017
…olic link was added: $GS_HOME/server/stones/<stone-name>/tode that references $GS_HOME/sys/local/server/stones/<stone-name> to make it possible to easily bounce to the tODE scripts the GemStone stone directory structure ...
@dalehenrich
Copy link
Member

oops that comment was aimed at a bug in a completely different project

@marianopeck
Copy link
Contributor Author

@dalehenrich sure, using the netldi name rather than port is much better

@dalehenrich
Copy link
Member

builds are green

@dalehenrich
Copy link
Member

There are issues with topaz running as rpc rather than linked with stdout going to the gem log instead of stdout, so we need to not include the gemnetid by default ... I think leaving it in and commenting it out is a good compromise

@dalehenrich dalehenrich reopened this May 19, 2017
@marianopeck
Copy link
Contributor Author

Yes, I agree it is a good compromise (workaround) until the topaz -l is honored even if that line is present.

dalehenrich added a commit that referenced this issue Jul 26, 2017
….4 the `-L` option will ignore the `set gemnetid`, but that is not quite good enough for GsDevKit_home, because earlier versions of topaz do not recognize `-L` option.
dalehenrich added a commit that referenced this issue Jul 26, 2017
@dalehenrich
Copy link
Member

set gemnetid now commented out ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants