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 
<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

Reply via email to