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 installation (running from a not-so-fast USB2 stick) performs just as > fast as my own installation in /opt on a SSD disk! WOW! If this works from a USB stick, cannot the build to USB be adapted to build into /usr/local? Leslie > > Enricos installation also come with some sugar that I would love to have in > the official builds, the indication of the build revision, see below. When > I build some days later than the SVN Update I get the current date (but a > build from some days ago). Build revision would help when checking > installers against eachother (BSF4ooRexx versus standalone for instance). > > Also I can confirm that rexx AND rxapi run as user „po“ in the USB build, > in a normal installation rxapi run as "root". > > rxapi seems to start only once the rexx process launches (intended I guess) > and I have to use kill to stop rxapi before ejecting. > > The first time after I had killed rxapi and reinstalled my own installation > I had a glitch: > > Searching for test containers.Segmentation fault: 11 > > But redoing the command it worked and the entire test suite ran without > problem, so not sure what happened. Maybe Enrico gets some idea? How should > one stop running the USB build in the most unintrusive way? > > This is a leap forward! > > Last login: Mon Nov 26 10:34:35 on ttys001 > > cd /Volumes/4GB > > source ooRexx_vars > > rexx -v > Open Object Rexx Version 5.0.0 Rev:11523 > Build date: Nov 22 2018 > Addressing mode: 64 > Copyright (c) 1995, 2004 IBM Corporation. All rights reserved. > Copyright (c) 2005-2018 Rexx Language Association. All rights reserved. > This program and the accompanying materials are made available under the > terms of the Common Public License v1.0 which accompanies this distribution > or at http://www.oorexx.org/license.html > > rexx rexxcps > > - REXXCPS 2.1 -- Measuring REXX clauses/second - > REXX version is: REXX-ooRexx_5.0.0(MT)_64-bit 6.05 22 Nov 2018 >System is: DARWIN >Averaging: 100 measures of 30 iterations > > Total (full DO): 0.00459054 secs (average of 100 measures of 30 iterations) > Time for one iteration (1000 clauses) was: 0.000153018 seconds > > Performance: 6535179 REXX clauses per second > > ./pathfind 1417 > > proc 1417: /Volumes/4GB/bin/rxapi > > Executing tests from .../ooRexx/utilities/rxqueue/rxQueue.testGroup > > ooTest Framework - Automated Test of the ooRexx Interpreter > > Interpreter:REXX-ooRexx_5.0.0(MT)_64-bit 6.05 22 Nov 2018 > OS Name:DARWIN > SysVersion: Darwin Darwin Kernel Version 16.7.0: Wed Oct 10 > 20:06:00 PDT 2018; root:xnu-3789.73.24~1/RELEASE_X86_64.16.7.0 > > Tests ran: 22398 > Assertions: 375164 > Failures: 0 > Errors: 0 > > File search:00:00:01.603582 > Suite construction: 00:00:01.395994 > Test execution: 00:03:05.549436 > Total time: 00:03:09.001582 > > Hälsningar/Regards/Grüsse, > P.O. Jonsson > oor...@jonases.se > > > Am 25.11.2018 um 18:26 schrieb Enrico Sorichetti via Oorexx-devel : > >> I have just started work on a solution that no longer requires a single > >> daemon for the platform but rather use a single process per Rexx user. > >> Right now, I'm working on refactoring the code a bit to make it easier > >> to plug in different management schemes, and the next step will be to > >> convert Windows, which is the version that will require the most new > >> code, then will address the *ix variants after that. I'll need so > >> assistance from somebody on that step as I don't have a Linux setup any > >> more. When this is all done, all of this daemon stuff, including the > >> writing of the PID files should go away and things will get a lot > >> simpler. > > > > As already told the only reason rxapi needs to be run as sudo is that it > > writes to /var/run > > > > I have already - in my sandbox - modified rxapi > > To get the OOREXX_PIDFILE environment variable and use it > > I use export OOREXX_PIDFILE=/tmp/ooRexx.pid > > > > And since SysLocalAPIManager starts the rxapi process > > Nothing has to be done > > > > I have been running for a few days with this setup and everything works > > as a charm > > > > I run successfully the test suite ( the native api section needs a few > > adjustments ) rexx testOORexx -s -X native_api with 0 errors > > > > I was able also to build a fully relocatable binary that can run from a > > usb stick with just a couple of exports The new PATH for the bin > > directory of rexx, the NLSPATH for the rexx.cat and the OOREXX_PIDFILE > > for the rxapi thing > > > > I have sent my binaries to P.O and Rony to have a confirmation of my > > findings As soon as they confirm
Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)
Running High Sierra I can run all tests (-API) with my own installation to /opt AND with the version made by Enrico for USB. On three different (but very similar) machines. I think that the reason for the incompatibility may indeed be „Mojave“. Later this week I will wipe one machine and install Mojave and see what differences this makes. This may well cause us som pain. I think of all the „deprecated“ things and other warnings coming out of the build process. @Rony: you do not need to do anything for the moment, once I have some different OS version it will be easier to compare installations. Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 26.11.2018 um 13:55 schrieb Rony G. Flatscher : > > Just a brief update on this list (and a private e-Mail to Enrico with more > infos). > > On 26.11.2018 00:04, Rony wrote: >> Thank you very much, will test it tomorrow when back at the office! > My Apple machine got updated to Mojave, should that make a difference as I > was only able to run > "rexx -e" from everywhere, but when trying to run a Rexx script on my machine > I get some "Failure > loading required base library“ > There might be something different/wrong on my Apple machine as P.O. reported > that he cannot get all > ooRexx test units execute successfully with the BSF4ooRexx installation > (whereas I can), but now he > has been able to succeed with the stick version. > > ---rony > > > > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)
Just a brief update on this list (and a private e-Mail to Enrico with more infos). On 26.11.2018 00:04, Rony wrote: > Thank you very much, will test it tomorrow when back at the office! My Apple machine got updated to Mojave, should that make a difference as I was only able to run "rexx -e" from everywhere, but when trying to run a Rexx script on my machine I get some "Failure loading required base library". There might be something different/wrong on my Apple machine as P.O. reported that he cannot get all ooRexx test units execute successfully with the BSF4ooRexx installation (whereas I can), but now he has been able to succeed with the stick version. ---rony ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)
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 installation (running from a not-so-fast USB2 stick) performs just as fast as my own installation in /opt on a SSD disk! WOW! Enricos installation also come with some sugar that I would love to have in the official builds, the indication of the build revision, see below. When I build some days later than the SVN Update I get the current date (but a build from some days ago). Build revision would help when checking installers against eachother (BSF4ooRexx versus standalone for instance). Also I can confirm that rexx AND rxapi run as user „po“ in the USB build, in a normal installation rxapi run as "root". rxapi seems to start only once the rexx process launches (intended I guess) and I have to use kill to stop rxapi before ejecting. The first time after I had killed rxapi and reinstalled my own installation I had a glitch: Searching for test containers.Segmentation fault: 11 But redoing the command it worked and the entire test suite ran without problem, so not sure what happened. Maybe Enrico gets some idea? How should one stop running the USB build in the most unintrusive way? This is a leap forward! Last login: Mon Nov 26 10:34:35 on ttys001 cd /Volumes/4GB source ooRexx_vars rexx -v Open Object Rexx Version 5.0.0 Rev:11523 Build date: Nov 22 2018 Addressing mode: 64 Copyright (c) 1995, 2004 IBM Corporation. All rights reserved. Copyright (c) 2005-2018 Rexx Language Association. All rights reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution or at http://www.oorexx.org/license.html rexx rexxcps - REXXCPS 2.1 -- Measuring REXX clauses/second - REXX version is: REXX-ooRexx_5.0.0(MT)_64-bit 6.05 22 Nov 2018 System is: DARWIN Averaging: 100 measures of 30 iterations Total (full DO): 0.00459054 secs (average of 100 measures of 30 iterations) Time for one iteration (1000 clauses) was: 0.000153018 seconds Performance: 6535179 REXX clauses per second ./pathfind 1417 proc 1417: /Volumes/4GB/bin/rxapi Executing tests from .../ooRexx/utilities/rxqueue/rxQueue.testGroup ooTest Framework - Automated Test of the ooRexx Interpreter Interpreter:REXX-ooRexx_5.0.0(MT)_64-bit 6.05 22 Nov 2018 OS Name:DARWIN SysVersion: Darwin Darwin Kernel Version 16.7.0: Wed Oct 10 20:06:00 PDT 2018; root:xnu-3789.73.24~1/RELEASE_X86_64.16.7.0 Tests ran: 22398 Assertions: 375164 Failures: 0 Errors: 0 File search:00:00:01.603582 Suite construction: 00:00:01.395994 Test execution: 00:03:05.549436 Total time: 00:03:09.001582 Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 25.11.2018 um 18:26 schrieb Enrico Sorichetti via Oorexx-devel > : > > >> I have just started work on a solution that no longer requires a single >> daemon for the platform but rather use a single process per Rexx user. Right >> now, I'm working on refactoring the code a bit to make it easier to plug in >> different management schemes, and the next step will be to convert Windows, >> which is the version that will require the most new code, then will address >> the *ix variants after that. I'll need so assistance from somebody on that >> step as I don't have a Linux setup any more. When this is all done, all of >> this daemon stuff, including the writing of the PID files should go away and >> things will get a lot simpler. > > As already told the only reason rxapi needs to be run as sudo is that it > writes to /var/run > > I have already - in my sandbox - modified rxapi > To get the OOREXX_PIDFILE environment variable and use it > I use export OOREXX_PIDFILE=/tmp/ooRexx.pid > > And since SysLocalAPIManager starts the rxapi process > Nothing has to be done > > I have been running for a few days with this setup and everything works as a > charm > > I run successfully the test suite ( the native api section needs a few > adjustments ) > rexx testOORexx -s -X native_api with 0 errors > > I was able also to build a fully relocatable binary that can run from a usb > stick with just a couple of exports > The new PATH for the bin directory of rexx, the NLSPATH for the rexx.cat and > the OOREXX_PIDFILE for the rxapi thing > > I have sent my binaries to P.O and Rony to have a confirmation of my findings > As soon as they confirm I will post a patch for wider testing > > Cheers > > Enrico > > > > > > > > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel ___
Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)
This should be independent of any particular distro. In theory, what I'm doing should work on any *ix based system. Rick On Sun, Nov 25, 2018 at 6:29 PM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > What Linux distro will You need … > I am pretty comfortable running centos if that is enough > Enrico > > > > On 26 Nov 2018, at 00:26, Rony wrote: > > > > > >> Am 26.11.2018 um 00:13 schrieb Rick McGuire : > >> > >> I need someone to do a little more than test it. I can write most of > the code, but cannot compile or debug it. If you can do nothing more than > try to build it for me once I have the Linux code written, that would be > great. > > Sure, I can do that! > > (Sometimes it may be the case that it may take a day or two if I am > pinned down in my day jpb. But as in the past I will try hard to help as > quickly as possible to keep the ball rolling.) > > > > —-rony > > > > Rony G. Flatscher (mobil/e) > > > > > > ___ > > Oorexx-devel mailing list > > Oorexx-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)
What Linux distro will You need … I am pretty comfortable running centos if that is enough Enrico > On 26 Nov 2018, at 00:26, Rony wrote: > > >> Am 26.11.2018 um 00:13 schrieb Rick McGuire : >> >> I need someone to do a little more than test it. I can write most of the >> code, but cannot compile or debug it. If you can do nothing more than try to >> build it for me once I have the Linux code written, that would be great. > Sure, I can do that! > (Sometimes it may be the case that it may take a day or two if I am pinned > down in my day jpb. But as in the past I will try hard to help as quickly as > possible to keep the ball rolling.) > > —-rony > > Rony G. Flatscher (mobil/e) > > > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)
> Am 26.11.2018 um 00:13 schrieb Rick McGuire : > > I need someone to do a little more than test it. I can write most of the > code, but cannot compile or debug it. If you can do nothing more than try to > build it for me once I have the Linux code written, that would be great. Sure, I can do that! (Sometimes it may be the case that it may take a day or two if I am pinned down in my day jpb. But as in the past I will try hard to help as quickly as possible to keep the ball rolling.) —-rony Rony G. Flatscher (mobil/e) ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)
I need someone to do a little more than test it. I can write most of the code, but cannot compile or debug it. If you can do nothing more than try to build it for me once I have the Linux code written, that would be great. Rick On Sun, Nov 25, 2018 at 6:08 PM Rony wrote: > > Am 25.11.2018 um 18:05 schrieb Rick McGuire > ... cut ... > > >> > I have just started work on a solution that no longer requires a single > daemon for the platform but rather use a single process per Rexx user. > Right now, I'm working on refactoring the code a bit to make it easier to > plug in different management schemes, and the next step will be to convert > Windows, which is the version that will require the most new code, then > will address the *ix variants after that. I'll need so assistance from > somebody on that step as I don't have a Linux setup any more. When this is > all done, all of this daemon stuff, including the writing of the PID files > should go away and things will get a lot simpler. > > > Wow, that is *great*! If necessary I volunteer to test the Linux part, > though there are better experienced ones who perhaps lend their hand! > > Good luck and cheers > > —-rony > > Rony G. Flatscher (mobil/e) > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)
> Am 26.11.2018 um 00:06 schrieb Rick McGuire : > > The approach I am working on does not use ports at all. This should get > around a lot of the issues with the current setup. That would be really *great*! —-rony Rony G. Flatscher (mobil/e) ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)
> Am 25.11.2018 um 18:05 schrieb Rick McGuire ... cut ... >> > > I have just started work on a solution that no longer requires a single > daemon for the platform but rather use a single process per Rexx user. Right > now, I'm working on refactoring the code a bit to make it easier to plug in > different management schemes, and the next step will be to convert Windows, > which is the version that will require the most new code, then will address > the *ix variants after that. I'll need so assistance from somebody on that > step as I don't have a Linux setup any more. When this is all done, all of > this daemon stuff, including the writing of the PID files should go away and > things will get a lot simpler. Wow, that is *great*! If necessary I volunteer to test the Linux part, though there are better experienced ones who perhaps lend their hand! Good luck and cheers —-rony Rony G. Flatscher (mobil/e)___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)
The approach I am working on does not use ports at all. This should get around a lot of the issues with the current setup. Rick On Sun, Nov 25, 2018 at 6:05 PM Rony wrote: > Thank you very much, will test it tomorrow when back at the office! > > One question: would it also be possible to use a different port in case it > got taken, despite it being registered fir ooRexx? > > Cheers > > —-rony > > Rony G. Flatscher (mobil/e) > > Am 25.11.2018 um 18:26 schrieb Enrico Sorichetti via Oorexx-devel < > oorexx-devel@lists.sourceforge.net>: > > > I have just started work on a solution that no longer requires a single > daemon for the platform but rather use a single process per Rexx user. > Right now, I'm working on refactoring the code a bit to make it easier to > plug in different management schemes, and the next step will be to convert > Windows, which is the version that will require the most new code, then > will address the *ix variants after that. I'll need so assistance from > somebody on that step as I don't have a Linux setup any more. When this is > all done, all of this daemon stuff, including the writing of the PID files > should go away and things will get a lot simpler. > > > As already told the only reason rxapi needs to be run as sudo is that it > writes to /var/run > > I have already - in my sandbox - modified rxapi > To get the OOREXX_PIDFILE environment variable and use it > I use export OOREXX_PIDFILE=/tmp/ooRexx.pid > > And since SysLocalAPIManager starts the rxapi process > Nothing has to be done > > I have been running for a few days with this setup and everything works as > a charm > > I run successfully the test suite ( the native api section needs a few > adjustments ) > rexx testOORexx -s -X native_api with 0 errors > > I was able also to build a fully relocatable binary that can run from a > usb stick with just a couple of exports > The new PATH for the bin directory of rexx, the NLSPATH for the rexx.cat > and the OOREXX_PIDFILE for the rxapi thing > > I have sent my binaries to P.O and Rony to have a confirmation of my > findings > As soon as they confirm I will post a patch for wider testing > > Cheers > > Enrico > > > > > > > > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)
Thank you very much, will test it tomorrow when back at the office! One question: would it also be possible to use a different port in case it got taken, despite it being registered fir ooRexx? Cheers —-rony Rony G. Flatscher (mobil/e) > Am 25.11.2018 um 18:26 schrieb Enrico Sorichetti via Oorexx-devel > : > > >> I have just started work on a solution that no longer requires a single >> daemon for the platform but rather use a single process per Rexx user. Right >> now, I'm working on refactoring the code a bit to make it easier to plug in >> different management schemes, and the next step will be to convert Windows, >> which is the version that will require the most new code, then will address >> the *ix variants after that. I'll need so assistance from somebody on that >> step as I don't have a Linux setup any more. When this is all done, all of >> this daemon stuff, including the writing of the PID files should go away and >> things will get a lot simpler. > > As already told the only reason rxapi needs to be run as sudo is that it > writes to /var/run > > I have already - in my sandbox - modified rxapi > To get the OOREXX_PIDFILE environment variable and use it > I use export OOREXX_PIDFILE=/tmp/ooRexx.pid > > And since SysLocalAPIManager starts the rxapi process > Nothing has to be done > > I have been running for a few days with this setup and everything works as a > charm > > I run successfully the test suite ( the native api section needs a few > adjustments ) > rexx testOORexx -s -X native_api with 0 errors > > I was able also to build a fully relocatable binary that can run from a usb > stick with just a couple of exports > The new PATH for the bin directory of rexx, the NLSPATH for the rexx.cat and > the OOREXX_PIDFILE for the rxapi thing > > I have sent my binaries to P.O and Rony to have a confirmation of my findings > As soon as they confirm I will post a patch for wider testing > > Cheers > > Enrico > > > > > > > > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)
> I have just started work on a solution that no longer requires a single > daemon for the platform but rather use a single process per Rexx user. Right > now, I'm working on refactoring the code a bit to make it easier to plug in > different management schemes, and the next step will be to convert Windows, > which is the version that will require the most new code, then will address > the *ix variants after that. I'll need so assistance from somebody on that > step as I don't have a Linux setup any more. When this is all done, all of > this daemon stuff, including the writing of the PID files should go away and > things will get a lot simpler. As already told the only reason rxapi needs to be run as sudo is that it writes to /var/run I have already - in my sandbox - modified rxapi To get the OOREXX_PIDFILE environment variable and use it I use export OOREXX_PIDFILE=/tmp/ooRexx.pid And since SysLocalAPIManager starts the rxapi process Nothing has to be done I have been running for a few days with this setup and everything works as a charm I run successfully the test suite ( the native api section needs a few adjustments ) rexx testOORexx -s -X native_api with 0 errors I was able also to build a fully relocatable binary that can run from a usb stick with just a couple of exports The new PATH for the bin directory of rexx, the NLSPATH for the rexx.cat and the OOREXX_PIDFILE for the rxapi thing I have sent my binaries to P.O and Rony to have a confirmation of my findings As soon as they confirm I will post a patch for wider testing Cheers Enrico ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)
On Sun, Nov 25, 2018 at 11:36 AM Rony G. Flatscher wrote: > Creating ooRexx from trunk from scratch into a new (empty) directory, > which will create the following rxapi-related files: > >- ./bin/rxapi >- ./bin/librexxapi.5.0.0.dylib >- ./bin/librexxapi.dylib -> librexxapi.5.0.0.dylib > > Then doing a "make install" which will use the created interpreter and > installs it to "~/Applications/ooRexx5.0.0". Here the following files with > "rxapi" in their names can be found: > >1. ./bin/rxapi (Nov 25, 2018) >2. ./bin/rxapid (Jul 7, 2017: a shell script) <--- ? >3. ./bin/librexxapi.dylib -> librexxapi.5.0.0.dylib (Nov 25, 2018) >4. ./share/ooRexx/rxapid.service (Aug 16, 2016) <--- ? >5. ./share/ooRexx/50-rxapid.preset (Aug 16, 2016) <---? > > So the current installation adds the files 2., 4., and 5. to the > installation directory. > > Definitely, 3. and 4. are outdated for MacOSX as they point to > "/usr/bin/rxapi" which is forbidden nowadays on MacOSX (only Apple is able > to install there, hence "/usr/local" for everyone else). They possibly > cannot work if the path to rxapi is wrong? > I believe all of those are part of the requirements for getting the system to automatically launch the daemon on system startup. It does sound like they are wrong for the Mac and may need adjustment, but I may have a better solution (see below). > > 3. is a bash script by Perry Werneck from 2013 that is based on > "OpenSUSE's" "/etc/init.d/sekeleton.compat". > > So my take would be that the current setup for MacOSX from ooRexx trunk > and CMake actually is wrong/outdated for Mac. Would others agree? > > --- > > Here all "rxapi" related files in the trunk source tree of ooRexx: > >- ./platform/unix/rxapid.service (Aug 16, 2016) >- ./platform/unix/macosx/org.rexxla.oorexx.rxapid.plist (Oct 2, 2018) ><-- only MacOSX related file, but not copied to installation! >- ./platform/unix/50-rxapid.preset (Aug 16,2016) >- ./rexxapi/server/platform/unix/rxapid (Jul 7, 2017) >- ./rexxapi/server/platform/windows/rxapi.ico (Sep 16, 2012) >- ./rexxapi/server/platform/windows/rxapi.rc (Jun 3, 2014) > > So the MacOSX installation should only copy > "./platform/unix/macosx/org.rexxla.oorexx.rxapid.plist" file and ignore all > others? > > --- > > As mentioned in another thread, BSF4ooRexx uses information of the past > years from the ooRexx developer list and uses the plist file > "org.rexxla.oorexx.rxapid.plist" (same as in > "./platform/unix/macosx/org.rexxla.oorexx.rxapid.plist") that defines the > rxapi daemon characteristics and post- and preflight scripts that use > "launchctl" to load or exit the rxapi daemon, which seems to work. > > It is sufficient to have a symbolic link in /Library/LaunchDaemons, > however the owner must be root and the group admin, otherwise (according to > my notes) a launchctl warning gets issued to the effect "launchctl: Dubious > ownership on file (skipping): > /Library/LaunchDaemons/org.rexxla.oorexx.rxapid.plist". > > The command to launch the rxapi daemon is (postflight script after initial > installation): > > launchctl load -w /Library/LaunchDaemons/org.rexxla.oorexx.rxapid.plist > > The command to unload the rxapi daemon is (preflight script before > deinstallation): > > launchctl unload -w /Library/LaunchDaemons/org.rexxla.oorexx.rxapid.plist > > --- > > There are others who have a real and deep knowledge in MacOSX (like Bruce > or Enrico), such that there may be better suited approaches. Maybe they > even could come up with solutions that could be applied to the project? > > I have just started work on a solution that no longer requires a single daemon for the platform but rather use a single process per Rexx user. Right now, I'm working on refactoring the code a bit to make it easier to plug in different management schemes, and the next step will be to convert Windows, which is the version that will require the most new code, then will address the *ix variants after that. I'll need so assistance from somebody on that step as I don't have a Linux setup any more. When this is all done, all of this daemon stuff, including the writing of the PID files should go away and things will get a lot simpler. Rick > ---rony > > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
