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.
Ad socket port number: doesn't the current code use another, free port, if there is a port clash and communicate the port to be used via that file? ---rony PS: Installation also could then allow for systemwide or user installation and deploy the respective rxapi. PPS: It would be just too much to ask the Rexx user to build the necessary rxapi version herself, so distributing both with ooRexx would really solve this long standing and nagging problem. Rony G. Flatscher (mobil/e) > Am 05.07.2016 um 20:24 schrieb Chip Davis <c...@aresti.com>: > > 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 7/5/2016 1:39 PM, Michael Lueck wrote: >> Greetings Chip, >> >> Chip Davis wrote: >>> Would you care to describe your magic incantation? >> >> >> >> Most of the documentation is in that RFE... >> >> >> "#542 Support non-root interpreter installation and execution on Unix-like >> systems" >> https://sourceforge.net/p/oorexx/feature-requests/542/ >> >> >> Specifically changing on of the ooRexx source files: >> >> rexxapi\server\platform\unix\APIService.cpp >> >> // For testing purposes comment out the following line to force RXAPI to >> // run as a foreground process. >> #undef RUN_AS_DAEMON >> >> #ifdef RUN_AS_DAEMON >> #define OOREXX_PIDFILE "/var/run/ooRexx.pid" >> bool run_as_daemon = true; >> #else >> #define OOREXX_PIDFILE >> "/kunden/homepages/35/d157794216/htdocs/opt/oorexx/var/run/ooRexx.pid" >> bool run_as_daemon = true; >> #endif >> >> >> Then building and installing from the patched source. >> >> My organization standard was to in my home directory build an opt/ >> directory, then package names as the next level... and to consider that >> directory as the virtual root. Thus .../var/run/ right where >> ooRexx wanted to place its PID file in the first place. >> >> I am thankful, >> > > ------------------------------------------------------------------------------ > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San > Francisco, CA to explore cutting-edge tech and listen to tech luminaries > present their vision of the future. This family event has something for > everyone, including kids. Get more information and register today. > http://sdm.link/attshape > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
