Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

Dear Erich, my apologies for not reading your answer thoroughly, I missed the delay that you had added in the server, now I can make it work exactly as intended. Thanks! The question with sending data delayed to the address with is still something that I would like to have, there is one test

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

Dear Erich,I can confirm that both scserver and sfserver works with r11517 (I was to late for r11516)With some modifications I could make the example code you provided work. Almost.Observation 1: it is not possible to send the to the server because then it will be closed before the clients are

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

How about a configuration option that would allow one to have the "#!/usr/bin/env rexx" hashbang applied instead (this way allowing the default to be overriden)? ---rony On 08.11.2018 15:00, P.O. Jonsson wrote: > > Hälsningar/Regards/Grüsse, > P.O. Jonsson > oor...@jonases.se

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 07.11.2018 um 23:21 schrieb Rick McGuire : > > > > On Wed, Nov 7, 2018 at 5:01 PM P.O. Jonsson > wrote: > Dear Rick and Erich, > > I have tried today to build on MAC using revision 11517.

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

On Wed, Nov 7, 2018 at 5:01 PM P.O. Jonsson wrote: > Dear Rick and Erich, > > I have tried today to build on MAC using revision 11517. Unfortunately the > Shebang comes out as *#!/opt/oorexx5.0.0/bin/rexx* rather as the intended > *#!/usr/bin/env > rexx* > > I copied the line > > set

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

I like the new shebang variable after looking at it. I can build and install both 32 and 64 at the same time or choose. It gets the samples shebang right. ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

On Wed, Nov 7, 2018 at 5:01 PM P.O. Jonsson wrote: > Dear Rick and Erich, > > I have tried today to build on MAC using revision 11517. Unfortunately the > Shebang comes out as *#!/opt/oorexx5.0.0/bin/rexx* rather as the intended > *#!/usr/bin/env > rexx* > That IS the intended Shebang line. It

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

Works for me using '127.0.0.1' On 11/06/18 12:52 PM, Erich Steinböck wrote: You might use something like below to run an automated test ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

I really have not got into the ZONES stuff yet. From the man page. The gethostid() function returns the 32-bit identifier for the current host. If the hardware capability exists, this identifier is taken from platform-dependent stable storage; otherwise it is a randomly generated number.  It is

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

> > Not sure where 119.242.25.32 is coming from > $ rexx -e "say SockGetHostId(); ::requires 'rxsock' LIBRARY" > 119.242.25.32 > Probably from /etc/hosts .. check the gethostid() docs for your OS. You can rewrite the samples to use localhost 127.0.0.1 instead - this should always work

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

agrellum@openindiana:~$ rexx -e "say SockGetHostId(); ::requires 'rxsock' LIBRARY" 119.242.25.32 agrellum@openindiana:~$ On 11/06/18 07:06 PM, Jason Martin wrote: agrellum@openindiana:~/ZZ$ rexx sfserver.rex Server listening at 119.242.25.32:50010 SockBind failed: EADDRNOTAVAIL Press [Enter]

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

This is purely my fault. Pulled examples from checkout. On 11/06/18 07:20 PM, Jason Martin wrote: Could you check that this has picked up the correct location for your version? Will do tomorrow. ___ Oorexx-devel mailing list

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

Could you check that this has picked up the correct location for your version? Will do tomorrow. ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

agrellum@openindiana:~/ZZ$ rexx sfserver.rex Server listening at 119.242.25.32:50010 SockBind failed: EADDRNOTAVAIL Press [Enter] To Shutdown Not sure where 119.242.25.32 is coming from Test groups all passed ___ Oorexx-devel mailing list

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

> > SockBind failed: EADDRNOTAVAIL > Jason, can you move sfserver.rex line 106 'say "Sever listening ..' before the bind to line 92, so that we can see address and port? Do you see the same result when you start scserver.rex? Does the socketClass.testGroup run fine with your build?

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

On Tue, Nov 6, 2018 at 3:09 PM Jason Martin wrote: > r11517 on OpenIndiana > > rexx sfserver.rex > > SockBind failed: EADDRNOTAVAIL > > Maybe? https://idea.popcount.org/2014-04-03-bind-before-connect/ > > Also? New to me. > > #!@OOREXX_SHEBANG_PROGRAM@ > This is something new in the build.

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

r11517 on OpenIndiana rexx sfserver.rex SockBind failed: EADDRNOTAVAIL Maybe? https://idea.popcount.org/2014-04-03-bind-before-connect/ Also? New to me. #!@OOREXX_SHEBANG_PROGRAM@ ___ Oorexx-devel mailing list

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

Commit [r11516] should fix the issues. can you advice how one can refer to two different terminal sessions in the > same program (with the intention to start the scserver in one ADDRESS > statement first and then the scclient in another ADDRESS

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

Ok thanks, I did not want to call it a bug. The test case is written so that once the issue is fixed it will flag a failure on that test (confirming that it works) and the test can be rewritten in a more meaningful way. The same problem is present also in sfserver/sfclient, a slightly

Re: [Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

> > But I noticed that I could not restart the server in about on minute after > I had closed it. Is this an expected behavior > Hi P.O, I can confirm the issue. It is probably caused by a bug in the Unix ooRexx sockets implementation. I've opened [bugs:#1570] Socket issues.

[Oorexx-devel] Advice needed on scserver.rex and scclient.rex sample programs

Dear developers, I have been testing the scclient-scserver example and it works well communicating between two terminal sessions (on a Mac). But I noticed that I could not restart the server in about on minute after I had closed it. Is this an expected behavior? I read in the example code that