[Oorexx-devel] Fwd: [Oorexx-svn] SF.net SVN: oorexx-code-0:[11085] test/trunk/ooRexx/extensions/platform/ unix/rxunixsys/SysUnix.testGroup

By enabling the "rxunixsys" tests with below change, a quirk has emerged: we've got two SysMkDir() functions, one in rexxutil which takes one arg, and the other in rxunixsys, which takes two args. Now we're failing two (unrelated) regression tests (STREAM bif, QUALIFY bif) which use SysMkDir with

Re: [Oorexx-devel] Running ooRexx without superuser power ... (Re: ooRexxUnit return codes

On Sat, Jul 2, 2016 at 11:44 AM, Rony G. Flatscher wrote: > Changed the subject to reflect this thread of discussion. > > The desire of many: allow ooRexx to be run off an USB stick to show > off/demonstrate ooRexx to others and/or have a great tool on ones hands to >

Re: [Oorexx-devel] macOS CMake changes

In the installer there is a place that it gives you the option of installing for the current user (~/Applications) or all users (/Applications) > On Jul 5, 2016, at 6:55 AM, René Jansen wrote: > > Hi Jack, > > it has been there for some installers in the past. It requires

Re: [Oorexx-devel] macOS CMake changes

I’ve been wanting to do this for years. Bruce > On Jul 5, 2016, at 5:16 AM, René Jansen wrote: > > With the introduction of El Capitan Apple introduced SIP - System Integrity > Protection, which makes it (without fiddling with NVRAM parameters to disable > it) impossible

Re: [Oorexx-devel] Running ooRexx without superuser power ... (Re: ooRexxUnit return codes

The problem with a shared environment is that you will never know if someone else is running ooRexx, and if it is a different version, and they get their rxapi started first, your program will fail, and it won’t be obvious why it fails. > On Jul 5, 2016, at 1:48 PM, Michael Lueck

Re: [Oorexx-devel] Running ooRexx without superuser power ... (Re: ooRexxUnit return codes

Greetings Bruce, CVBruce wrote: > Moving the PID file will only allow one user to run ooRexx in a shared > environment. Thank you for clarifying that. Noted. I am thankful, -- Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/

Re: [Oorexx-devel] Running ooRexx without superuser power ... (Re: ooRexxUnit return codes

Although this gets around the pid file problem, it doesn’t get around the port problem, you can still only run one rxapi process per computer. For example you can’t run both 32bit and 64bit rxapi concurrently on the same box, even if your have different pid files. You can’t run ooRexx V4.2

Re: [Oorexx-devel] Running ooRexx without superuser power ... (Re: ooRexxUnit return codes

That is a symptom. The reason it is set up that way is that communication is via port 10010 (or 10100, I forget which). Only one process can bind that port to accept incoming connections. The PID file is to prevent two processes from binding the ‘ooRexx’ port, thus preventing one process

Re: [Oorexx-devel] Running ooRexx without superuser power ... (Re: ooRexxUnit return codes

One possibility would be to create and distribute *both* versions of rxapi with ooRexx, one as daemon (root/sudo mandatory), one as user related. A user like Chip or myself could then swap to the needed rxapi version and get running oRexx even on a web server in user space or from a USB stick.

Re: [Oorexx-devel] Running ooRexx without superuser power ... (Re: ooRexxUnit return codes

My apologies. I missed the fact that the only way you were able to run ooRexx on a Shared Server was to patch and rebuilt the processor from source. Not likely we'll get much interest from users on shared or corporate Linux systems with that requirement. I've upvoted your RFE. -Chip- On

Re: [Oorexx-devel] Running ooRexx without superuser power ... (Re: ooRexxUnit return codes

CVBruce wrote: > I don't think that the issue is really the PID file. Running RxAPI as a user ID other than root will not have permissions to /var/run to write the PID file. > Rxapi binds a port, and only one process on the computer can bind that port > at a time, thus the PID file. All

Re: [Oorexx-devel] Running ooRexx without superuser power ... (Re: ooRexxUnit return codes

I don't think that the issue is really the PID file. Rxapi binds a port, and only one process on the computer can bind that port at a time, thus the PID file. All oorexx instances that are using rxapi on that computer, regardless of of process owner, talk to that bound, "well know" port.

Re: [Oorexx-devel] Running ooRexx without superuser power ... (Re: ooRexxUnit return codes

Michael, I have a couple of those Shared Web Hosting accounts, primarily to support a cluster of Mailman listservers. I had always thought that there was no way to install ooRexx on any of them for exactly the reason you describe: no root access and/or the lack of directory permissions.

[Oorexx-devel] optimizing build

To answer my own question, an optimizing build is done with: cmake -DCMAKE_BUILD_TYPE=Release ../code-0/main/trunk with this, CPS goes from 1.3M CPS to a respectable 5.9M CPS on this 2.2GHz i7. I am going to change to these on the build machine. best regards, René.

Re: [Oorexx-devel] macOS CMake changes

Hi Jack, it has been there for some installers in the past. It requires root, but it might be an option for the pkg installer. The trend on macOS, however, seems to indicate /Applications. in any case, it is easy to change. best regards, René. > On 5 jul. 2016, at 15:47, Jack Woehr

Re: [Oorexx-devel] macOS CMake changes

René Jansen wrote: > I also think that this makes for more clarity than /usr/local/bin and > /usr/local/lib, either to find things or to > uninstall them. How about /opt/oorexx -- Jack Woehr # "There's too much emphasis on things Box 51, Golden CO 80402 # like pawn structure

[Oorexx-devel] macOS CMake changes

With the introduction of El Capitan Apple introduced SIP - System Integrity Protection, which makes it (without fiddling with NVRAM parameters to disable it) impossible to write to /usr/bin. I do not think we can ask ooRexx users to disable this feature, and it should not be necessary. The

Re: [Oorexx-devel] [Announce] Welcome Erico Mendonca as a committer on the ooRexx project

+I ---rony Rony G. Flatscher (mobil/e) > Am 04.07.2016 um 19:33 schrieb Jon Wolfers : > > Erico has been working consistently on the build team for the project. > The Committers and the RexxLa have invited him to become a committer and I'm > very happy to say that he has