startnetldi -p does not exists anymore in 3.2.9, alternative is /etc/services?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

startnetldi -p does not exists anymore in 3.2.9, alternative is /etc/services?

GLASS mailing list
Hi guys, 

I found out that the argument -p does not exist anymore in 3.2.9 and it doesn't seem there is a replacement. Is /etc/services the alternative and desired solution?

Thanks in advance, 

--

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: startnetldi -p does not exists anymore in 3.2.9, alternative is /etc/services?

GLASS mailing list
There is a -P option. (That's an uppercase P.)

rsargent@galbadia run2 $ startnetldi -?
startnetldi: invalid option -?
Usage: startnetldi [-h] [-d] [-g|-s] [-n] [-a account] [-l logFile]
                  [-t seconds] [-P portNumber] [-A address] [name]
  where -h    prints usage information and exits.
        -b    maximum client connection backlog (default: 64).
        -d    cause netldi to print extra information to its log file.
        -g    start netldi in guest mode.
        -s    start netldi in secure mode.
        -n    netldi will not use adhoc scripts.
        -a    all processes started by the netldi will belong to this account.
        -l    specifies the name of the netldi log file.
        -t    number of seconds netldi will wait for child process to start.
        -v    print version and exit.
        -P    specifies the well-known port number that netldi will use.
        -A    specifies address to listen on, (up to 10 -A args accepted)
              If -A omitted, the default wildcard address ::  is listened on.
              If -A ::  is given, then other -A arguments are ignored.
              If -A is given, and neither -A :: nor -A ::1 are specified, then
              the loopback address ::1 is also listened on.
              The argument to -A may be a named or numeric address of a network
              interface on this machine.
        name  is the name of the netldi to start.
              If name is not specified, netldi name is taken from GEMSTONE_NRS_ALL
              environment variable (if available), otherwise default is gs64ldi
              If -P omitted, 'name' is looked up in the network services database



On Wed, Oct 21, 2015 at 9:22 AM, Mariano Martinez Peck via Glass <[hidden email]> wrote:
Hi guys, 

I found out that the argument -p does not exist anymore in 3.2.9 and it doesn't seem there is a replacement. Is /etc/services the alternative and desired solution?

Thanks in advance, 

--

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass



_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: startnetldi -p does not exists anymore in 3.2.9, alternative is /etc/services?

GLASS mailing list
Yes, but -P is different. When you want to connect from tODE from a remote/client machine for example, (if you do not use /etc/services) besides doing a port forwarding of the port of -P you also must port forward those which were (previously) specified in -p (that was a range of ports). 
So it seems the only way to do port forwarding now is using /etc/services. 



On Wed, Oct 21, 2015 at 1:32 PM, Richard Sargent <[hidden email]> wrote:
There is a -P option. (That's an uppercase P.)

rsargent@galbadia run2 $ startnetldi -?
startnetldi: invalid option -?
Usage: startnetldi [-h] [-d] [-g|-s] [-n] [-a account] [-l logFile]
                  [-t seconds] [-P portNumber] [-A address] [name]
  where -h    prints usage information and exits.
        -b    maximum client connection backlog (default: 64).
        -d    cause netldi to print extra information to its log file.
        -g    start netldi in guest mode.
        -s    start netldi in secure mode.
        -n    netldi will not use adhoc scripts.
        -a    all processes started by the netldi will belong to this account.
        -l    specifies the name of the netldi log file.
        -t    number of seconds netldi will wait for child process to start.
        -v    print version and exit.
        -P    specifies the well-known port number that netldi will use.
        -A    specifies address to listen on, (up to 10 -A args accepted)
              If -A omitted, the default wildcard address ::  is listened on.
              If -A ::  is given, then other -A arguments are ignored.
              If -A is given, and neither -A :: nor -A ::1 are specified, then
              the loopback address ::1 is also listened on.
              The argument to -A may be a named or numeric address of a network
              interface on this machine.
        name  is the name of the netldi to start.
              If name is not specified, netldi name is taken from GEMSTONE_NRS_ALL
              environment variable (if available), otherwise default is gs64ldi
              If -P omitted, 'name' is looked up in the network services database



On Wed, Oct 21, 2015 at 9:22 AM, Mariano Martinez Peck via Glass <[hidden email]> wrote:
Hi guys, 

I found out that the argument -p does not exist anymore in 3.2.9 and it doesn't seem there is a replacement. Is /etc/services the alternative and desired solution?

Thanks in advance, 

--

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass





--

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: startnetldi -p does not exists anymore in 3.2.9, alternative is /etc/services?

GLASS mailing list
The -p is not needed in 3.2 no port range needed...  the socket created with the connection to the netldi port (-P option) is kept alive by the gem instead of reconnecting on a different port --- which was the old mechanism ...

So for 3.2 and beyond only the explicit port (or /etc/services entry) need to be specified ...

Dale

On 10/21/2015 09:35 AM, Mariano Martinez Peck via Glass wrote:
Yes, but -P is different. When you want to connect from tODE from a remote/client machine for example, (if you do not use /etc/services) besides doing a port forwarding of the port of -P you also must port forward those which were (previously) specified in -p (that was a range of ports). 
So it seems the only way to do port forwarding now is using /etc/services. 



On Wed, Oct 21, 2015 at 1:32 PM, Richard Sargent <[hidden email]> wrote:
There is a -P option. (That's an uppercase P.)

rsargent@galbadia run2 $ startnetldi -?
startnetldi: invalid option -?
Usage: startnetldi [-h] [-d] [-g|-s] [-n] [-a account] [-l logFile]
                  [-t seconds] [-P portNumber] [-A address] [name]
  where -h    prints usage information and exits.
        -b    maximum client connection backlog (default: 64).
        -d    cause netldi to print extra information to its log file.
        -g    start netldi in guest mode.
        -s    start netldi in secure mode.
        -n    netldi will not use adhoc scripts.
        -a    all processes started by the netldi will belong to this account.
        -l    specifies the name of the netldi log file.
        -t    number of seconds netldi will wait for child process to start.
        -v    print version and exit.
        -P    specifies the well-known port number that netldi will use.
        -A    specifies address to listen on, (up to 10 -A args accepted)
              If -A omitted, the default wildcard address ::  is listened on.
              If -A ::  is given, then other -A arguments are ignored.
              If -A is given, and neither -A :: nor -A ::1 are specified, then
              the loopback address ::1 is also listened on.
              The argument to -A may be a named or numeric address of a network
              interface on this machine.
        name  is the name of the netldi to start.
              If name is not specified, netldi name is taken from GEMSTONE_NRS_ALL
              environment variable (if available), otherwise default is gs64ldi
              If -P omitted, 'name' is looked up in the network services database



On Wed, Oct 21, 2015 at 9:22 AM, Mariano Martinez Peck via Glass <[hidden email]> wrote:
Hi guys, 

I found out that the argument -p does not exist anymore in 3.2.9 and it doesn't seem there is a replacement. Is /etc/services the alternative and desired solution?

Thanks in advance, 

--

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass





--


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: startnetldi -p does not exists anymore in 3.2.9, alternative is /etc/services?

GLASS mailing list
OK, perfect. Thanks for the explanation. 

On Wed, Oct 21, 2015 at 2:25 PM, Dale Henrichs via Glass <[hidden email]> wrote:
The -p is not needed in 3.2 no port range needed...  the socket created with the connection to the netldi port (-P option) is kept alive by the gem instead of reconnecting on a different port --- which was the old mechanism ...

So for 3.2 and beyond only the explicit port (or /etc/services entry) need to be specified ...

Dale


On 10/21/2015 09:35 AM, Mariano Martinez Peck via Glass wrote:
Yes, but -P is different. When you want to connect from tODE from a remote/client machine for example, (if you do not use /etc/services) besides doing a port forwarding of the port of -P you also must port forward those which were (previously) specified in -p (that was a range of ports). 
So it seems the only way to do port forwarding now is using /etc/services. 



On Wed, Oct 21, 2015 at 1:32 PM, Richard Sargent <[hidden email]> wrote:
There is a -P option. (That's an uppercase P.)

rsargent@galbadia run2 $ startnetldi -?
startnetldi: invalid option -?
Usage: startnetldi [-h] [-d] [-g|-s] [-n] [-a account] [-l logFile]
                  [-t seconds] [-P portNumber] [-A address] [name]
  where -h    prints usage information and exits.
        -b    maximum client connection backlog (default: 64).
        -d    cause netldi to print extra information to its log file.
        -g    start netldi in guest mode.
        -s    start netldi in secure mode.
        -n    netldi will not use adhoc scripts.
        -a    all processes started by the netldi will belong to this account.
        -l    specifies the name of the netldi log file.
        -t    number of seconds netldi will wait for child process to start.
        -v    print version and exit.
        -P    specifies the well-known port number that netldi will use.
        -A    specifies address to listen on, (up to 10 -A args accepted)
              If -A omitted, the default wildcard address ::  is listened on.
              If -A ::  is given, then other -A arguments are ignored.
              If -A is given, and neither -A :: nor -A ::1 are specified, then
              the loopback address ::1 is also listened on.
              The argument to -A may be a named or numeric address of a network
              interface on this machine.
        name  is the name of the netldi to start.
              If name is not specified, netldi name is taken from GEMSTONE_NRS_ALL
              environment variable (if available), otherwise default is gs64ldi
              If -P omitted, 'name' is looked up in the network services database



On Wed, Oct 21, 2015 at 9:22 AM, Mariano Martinez Peck via Glass <[hidden email][hidden email]> wrote:
Hi guys, 

I found out that the argument -p does not exist anymore in 3.2.9 and it doesn't seem there is a replacement. Is /etc/services the alternative and desired solution?

Thanks in advance, 

--

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass





--


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass




--

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass