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 bring along when checking out
problematic computers or
helping collegues and friends.
Currently this is not possible on computers, where the user has no superuser
power over the
computer, which is a great pity. This scenario is quite usual, when computers
are deployed in
business environments, where root/superuser power is reserved for the
installation, maintenance
teams and the like.
The reason for this restriction seems to be how rxapi gets started and used.
So maybe a few questions therefore about rxapi:
* What is the rationale of allowing only one rxapi running per computer?
* What is the rationale to allow to install it with root/superuser rights
only?
* Would it be theoretically possible to run separate instances of rxapi for
different user
sessions (one per session) by default, one may be a root/superuser/daemon
session?
Ad port number: even though there is a reserved port for ooRexx, this does not
guarantee that it
would be available at all on any computer. So in the case of a port clash (port
already in use by a
different program at rxapi startup) communicating the rxapi port to Rexx
clients needs to be done
one way or the other.
Ad users killing rxapi and thereby affecting running ooRexx programs in
multiuser environments: this
would be possible for sudo users at all times and doing it is even mandatory
for upgrading ooRexx
currently. (In a normal use case of ooRexx programs, users would not even know
about rxapi so would
not know to kill it.)
---rony
P.S.: Even if this is not tackled for 5.0, it would help deciding changes for
the future, if more
information was available about the rationales behind rxapi. It for sure would
help spreading the
word about ooRexx by demonstration of its capabilities tremendeously.
On 01.07.2016 16:57, René Jansen wrote:
> Hi Erich,
>
> I’ll work on trying to get these packages available, at least the ones that
> Erico does not provide.
>
> Yes, we should not change anything for this release. I entirely agree. Still,
> I am not convinced
> that ooRexx needs a designated port at all; much less a deamon process
> running as root. But we
> will study and discuss in due time.
>
> I’ll try to fix the Z installation. Did not know about the rexx.cat bug.
> Indeed, file rexx.cat
> now reports:
> rexx.cat: Nazgul style compiled message catalog, version 1
>
> instead as data what it used to do.
>
> best regards,
>
> René.
>
>
>> On 1 jul. 2016, at 16:45, Erich Steinböck <erich.steinbo...@gmail.com
>> <mailto:erich.steinbo...@gmail.com>> wrote:
>>
>> afaik that is done with cpack and documented in Cmake-build-readme.txt
>> Thanks for the pointer. These package files are exactly what we should make
>> available to our
>> users for beta-testing
>>
>> I do not know the cross-process requirements of rxapi
>> rxapi listens on port 10010. It is a system-wide demon - there can only be
>> one demon listening
>> on port 10010. 10010 is the official port for ooRexx,
>> see
>> https://en.m.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers#Well-known_ports
>>
>> how could we localize that, possibly running over different port numbers or
>> just
>> sockets/pipes localized to the user
>> I cannot imagine anyone doing a change of this magnitude - we really should
>> push for beta and
>> then release
>>
>> I also looked at the Z build - could you tell me why this is related to
>> running from the build dir?
>> the test is running off build/bin, but the rexx.cat it sees, is from an
>> older "make install"
>> version. We had a bug concerning how rexx.cat was being built, that I just
>> recently fixed -
>> that's why the two versions are different and that's why a few tests fail,
>> which check for exact
>> message texts
>> There may be other things that are being picked up from an installed rexx
>> when running from
>> build/bin, but I haven't checked that
>>
>> Erich
------------------------------------------------------------------------------
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
