Re: [Oorexx-devel] Time for the *ix users to pitch in.

> > One thing that needs to be checked out is what happens if a second version > of rxapi gets launched. > .. there's also some code to unlink() the file before the bind operation > that I'm hoping will fail if the socket is still in use. On Linux, rxapi can be started a second time, with both of

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Rats. Looks like there is still a need for a .pid file. Fortunately, we can store it in the same location, so there are still no privileges required. The code can pretty much be copied from the old version. Rick On Sat, Dec 1, 2018 at 8:54 AM Erich Steinböck wrote: > One thing that needs to be

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Erich, One more experiment. Since there is some automatic cleanup involved with that file because of its location, could you try this again after commenting out the call to the method that performs the unlink(). From what I've read, the second bind should fail, which will cause the second instance

Re: [Oorexx-devel] Time for the *ix users to pitch in.

> > try this again after commenting out the call to the method that performs > the unlink(). > If I comment out the call to checkServiceName, the bind fails (and with it rxapi) even the "first" time, unless I manually remove the $XDG_RUNTIME_DIR/.ooRexx-5.0.0-64.service special file kill the first

Re: [Oorexx-devel] Time for the *ix users to pitch in.

This question seems to exactly cover our situation: https://stackoverflow.com/questions/30742508/linux-local-communication-sockets-why-is-bind-not-failing-as-expected The solution seems to better than what I proposed On Sat, Dec 1, 2018 at 4:13 PM Erich Steinböck wrote: > try this again after c

[Oorexx-devel] Ad installation on Linux and MacOS ... (Re: Time for the *ix users to pitch in.

When creating the deb-package for Ubuntu-Linux installing (and uninstalling) it will report an error: Installation: rony@rony-linux:~/work/oorexx/rick_rxapi_sandbox$ sudo dpkg -i ooRexx-5.0.0-11547.ubuntu1404.x86_64.deb Selecting previously unselected package oorexx. (Reading d

Re: [Oorexx-devel] Ad installation on Linux and MacOS ... (Re: Time for the *ix users to pitch in.

Thought I had caught all of those. Just committed a fix. Rick On Sat, Dec 1, 2018 at 11:06 AM Rony G. Flatscher wrote: > When creating the deb-package for Ubuntu-Linux installing (and > uninstalling) it will report an error: > > Installation: > > rony@rony-linux:~/work/oorexx/rick_rxapi_sandbox

Re: [Oorexx-devel] Time for the *ix users to pitch in.

I found a fairly simple example of using a lock file that was simpler than using a pid file, so went with that. Rick On Sat, Dec 1, 2018 at 10:48 AM Erich Steinböck wrote: > This question seems to exactly cover our situation: > > https://stackoverflow.com/questions/30742508/linux-local-communic

Re: [Oorexx-devel] Time for the *ix users to pitch in.

Fresh build, trying to compile until: [ 76%] Building CXX object CMakeFiles/rxapi.dir/rexxapi/server/platform/unix/linux/APIService.cpp.o /home/rony/dev/oorexx-code-0/sandbox/rick/rxapi/rexxapi/server/platform/unix/linux/APIService.cpp: In function ´int acquireLock(const char*)`: /

Re: [Oorexx-devel] Ad installation on Linux and MacOS ... (Re: Time for the *ix users to pitch in.

There are some typos to fix .. Unlink instead of online PATH_MAX instead of MAX_PATH lockFd instead of lockfd E > On 1 Dec 2018, at 17:24, Rick McGuire wrote: > > Thought I had caught all of those. Just committed a fix. > > Rick > > On Sat, Dec 1, 2018 at 11:06 AM Rony G. Flatscher

Re: [Oorexx-devel] Ad installation on Linux and MacOS ... (Re: Time for the *ix users to pitch in.

On 01.12.2018 17:33, Enrico Sorichetti via Oorexx-devel wrote: > There are some typos to fix .. > Unlink instead of online  > PATH_MAX instead of MAX_PATH > lockFd instead of lockfd Thank you Erich, that made it pass! ---rony > > >> On 1 Dec 2018, at 17:24, Rick McGuire >

Re: [Oorexx-devel] Ad installation on Linux and MacOS ... (Re: Time for the *ix users to pitch in.

Version 17.7.0: Wed Oct 10 23:06:14 PDT 2018; root:xnu-4570.71.13~1/RELEASE_X86_64.17.7.0 Tests ran: 22398 Assertions: 375189 Failures: 4 Errors: 0 [failure] [20181201 17:55:24.490826] svn:r11522 Change date: 2018-11-22 01:34:56 +0100 Test

Re: [Oorexx-devel] Ad installation on Linux and MacOS ... (Re: Time for the *ix users to pitch in.

On 01.12.2018 17:24, Rick McGuire wrote: > Thought I had caught all of those. Just committed a fix. Thank you very much! LINUX: Rev. 11549 can be installed and uninstalled without any error messages. The ooRexx test suite runs through (with "-X native_API"). MacOS: Rev. 11549: the

Re: [Oorexx-devel] Ad installation on Linux and MacOS ... (Re: Time for the *ix users to pitch in.

Does the Mac not set the $XDG_RUNTIME_DIR environment variable? On Sat, Dec 1, 2018 at 12:33 PM Rony G. Flatscher wrote: > On 01.12.2018 17:24, Rick McGuire wrote: > > Thought I had caught all of those. Just committed a fix. > > Thank you very much! > > LINUX: > > Rev. 11549 can be installed and

Re: [Oorexx-devel] Ad installation on Linux and MacOS ... (Re: Time for the *ix users to pitch in.

On 01.12.2018 18:39, Rick McGuire wrote: > Does the Mac not set the $XDG_RUNTIME_DIR environment variable? No, this is a Linux thing only. ---rony ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/lis

Re: [Oorexx-devel] Ad installation on Linux and MacOS ... (Re: Time for the *ix users to pitch in.

Sorry, was too fast: . ---rony On 01.12.2018 18:41, Rony G. Flatscher wrote: > On 01.12.2018 18:39, Rick McGuire wrote: >> Does the Mac not set the $XDG_RUNTIME_DIR environment variable? > No, this is a Linux thing only. > > ---rony >

Re: [Oorexx-devel] Ad installation on Linux and MacOS ... (Re: Time for the *ix users to pitch in.

The same observation as on MacOS can be experienced on Linux (same four failures in "rxQueue.testGroup"). ---rony On 01.12.2018 18:33, Rony G. Flatscher wrote: > On 01.12.2018 17:24, Rick McGuire wrote: >> Thought I had caught all of those. Just committed a fix. > Thank you very much! > > LINUX

Re: [Oorexx-devel] Ad installation on Linux and MacOS ... (Re: Time for the *ix users to pitch in.

IMO for the macro space thing things are a bit murky, Running [enrico@enrico-imac ooRexx.testsuite]$rexx testOORexx.rex -s -X native_api I get the five BOINGs but ooTest Framework - Automated Test of the ooRexx Interpreter Interpreter:REXX-ooRexx_5.0.0(MT)_64-bit 6.05 1 Dec 2018 OS Nam

Re: [Oorexx-devel] Ad installation on Linux and MacOS ... (Re: Time for the *ix users to pitch in.

After the first failure Running rexx testOORexx.rex -f rxQueue.testGroup Did not report any error E > On 1 Dec 2018, at 18:50, Rony G. Flatscher wrote: > > The same observation as on MacOS can be experienced on Linux (same four > failures in "rxQueue.testGroup"). > > ---rony > > On 0

Re: [Oorexx-devel] Ad installation on Linux and MacOS ... (Re: Time for the *ix users to pitch in.

Did an uninstall of rev 11549 on LINUX: rxapi was still running (killed it with "kill -1") the lock an service files ".oorexx-5.0.0-64.*" were still in XDG_RUNTIME_DIR ("/run/user/1000"), so deleted them there Checked out rev 11550, recreated the ooRexx LINUX interpreter and installe

Re: [Oorexx-devel] Ad installation on Linux and MacOS ... (Re: Time for the *ix users to pitch in.

You might want to try again with the latest rev. Also, what happens if you run the full test suite a second time (vs. running just the one test group). Rick On Sat, Dec 1, 2018 at 12:50 PM Rony G. Flatscher wrote: > The same observation as on MacOS can be experienced on Linux (same four > failu

[Oorexx-devel] A request for getting somehow the (svn) revision number of the current running/using ooRexx interpreter

Currently it is quite a time consuming effort to make sure that all the different ooRexx builds on all of the different operating systems have been built using the latest svn revision. It would be of great help in such situations, if it became possible to learn the (svn) revision number the cur

Re: [Oorexx-devel] Ad installation on Linux and MacOS ... (Re: Time for the *ix users to pitch in.

The latest commit to the rxapi sandbox builds and passes all tests on my Ubuntu 16.04 VM. Have never had any rxqueue or Macrospace test failures with any of the previous rxapi sandbox builds. On Sat, Dec 1, 2018 at 7:04 PM Rick McGuire wrote: > You might want to try again with the latest rev. Al

Re: [Oorexx-devel] Ad installation on Linux and MacOS ... (Re: Time for the *ix users to pitch in.

On 01.12.2018 19:16, Erich Steinböck wrote: > The latest commit to the rxapi sandbox builds and passes all tests on my > Ubuntu 16.04 VM. > Have never had any rxqueue or Macrospace test failures with any of the > previous rxapi sandbox builds. > Maybe the postings crossed: my posting from 19:02 r

Re: [Oorexx-devel] Ad installation on Linux and MacOS ... (Re: Time for the *ix users to pitch in.

Dear Enrico, The five „Boings“ come from the BIF BEEP.testGroup; on Windows you can play a cheesy little tune using the function beep(frequency, duration). I have used that to play „kings Quest“ on exit of a script (while on Windows, using IBM Rexx, in Neolithic times). On Mac it goes „Boing“ i

Re: [Oorexx-devel] A request for getting somehow the (svn) revision number of the current running/using ooRexx interpreter

I agree with Rony that a build number in the rexx -v would be very useful. I also have a number of systems and since the build is not linked to the day you actually compiled (that may be (much) later ) you are never really sure. Also I tried some times to make a standalone build to compare to th

Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)

On 2018-11-26 04:30:15 P.O. Jonsson wrote: > Dear all, > > I can confirm that Enricos installation runs (blazingly fast!) from a USB > stick on a MAC without any elevated user rights whatsoever. I have run the > complete test case suite (except the API) and they all work, see below. The > USB insta