Re: [Oorexx-devel] Any progress on non-root perms an ooRexx 4.x?

2013-04-18 Thread Michael Lueck
Well, based on this...

David Ashley wrote:
 Oh, there is one other point that may need to be cleared up.

 If you are not making an RPM or DEB file and instead are performing a
 make install to install ooRexx then you can feel free to supply any
 prefix you want because nothing the prefix will not be overridden in
 that scenario.

I went ahead and built from source v4.1.2.

Evaluating it today I discover...

(uiserver):u40009095:~/opt/oorexx/share/ooRexx  rexx rexxtry.rex say 
60648620/1024
 74 *-* push argrx
REX0048E: Error 48 running 
/homepages/35/d157794216/htdocs/opt/oorexx/share/ooRexx/rexxtry.rex line 74:  
Failure in system service
REX0425E: Error 48.1:  Failure in system service: SYSTEM QUEUE

(uiserver):u40009095:~/opt/oorexx/share/ooRexx  rexx -v
Open Object Rexx Version 4.1.2
Build date: Apr 12 2013
Addressing Mode: 32

Copyright (c) IBM Corporation 1995, 2004.
Copyright (c) RexxLA 2005-2012.
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


Please tell me there is another exponentiation for this than need root perms.

(I have a nagging suspicion that Rick did say something about a single queue 
service for the entire box, need root for v4 code, or something of the sort...)

Sincerely,

-- 
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/

--
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis  visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


Re: [Oorexx-devel] Any progress on non-root perms an ooRexx 4.x?

2013-04-18 Thread David Ashley
Sorry, but root permission is required for running the rexxapi program
on a *nix box. This is because it opens a local port for client
connections and only programs that run with root permissions can open a
server port on *nix systems.

This is one of the restrictions that raised it ugly head when we moved
from shared memory to sockets for communication between clients and the
rexxapi server program. It was a tradeoff between performance and
reliability (sockets are much more reliable).

You might try marking the rexxapi program as a sudo application and see
if that fixes the problem.

David Ashley

On Thu, 2013-04-18 at 16:34 -0400, Michael Lueck wrote:
 Well, based on this...
 
 David Ashley wrote:
  Oh, there is one other point that may need to be cleared up.
 
  If you are not making an RPM or DEB file and instead are performing a
  make install to install ooRexx then you can feel free to supply any
  prefix you want because nothing the prefix will not be overridden in
  that scenario.
 
 I went ahead and built from source v4.1.2.
 
 Evaluating it today I discover...
 
 (uiserver):u40009095:~/opt/oorexx/share/ooRexx  rexx rexxtry.rex say 
 60648620/1024
  74 *-* push argrx
 REX0048E: Error 48 running 
 /homepages/35/d157794216/htdocs/opt/oorexx/share/ooRexx/rexxtry.rex line 74:  
 Failure in system service
 REX0425E: Error 48.1:  Failure in system service: SYSTEM QUEUE
 
 (uiserver):u40009095:~/opt/oorexx/share/ooRexx  rexx -v
 Open Object Rexx Version 4.1.2
 Build date: Apr 12 2013
 Addressing Mode: 32
 
 Copyright (c) IBM Corporation 1995, 2004.
 Copyright (c) RexxLA 2005-2012.
 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
 
 
 Please tell me there is another exponentiation for this than need root 
 perms.
 
 (I have a nagging suspicion that Rick did say something about a single queue 
 service for the entire box, need root for v4 code, or something of the 
 sort...)
 
 Sincerely,
 



--
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis  visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


Re: [Oorexx-devel] Any progress on non-root perms an ooRexx 4.x?

2013-04-18 Thread Michael Lueck
David Ashley wrote:
 You might try marking the rexxapi program as a sudo application and see
 if that fixes the problem.

Without root/sudo perms to the share hosting server, I doubt I can accomplish 
this. Am I correct?

Disappointed indeed... :-(

Sincerely,

-- 
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/

--
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis  visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


Re: [Oorexx-devel] Any progress on non-root perms an ooRexx 4.x?

2013-04-18 Thread CVBruce
I may be wrong, but I thought that root was only required if the port was below 
a certain number, perhaps 1000.  Anything over this number could be opened by 
ordinary users.  Did I remember this incorrectly, or has this changed.

Bruce

Sent from an undisclosed location.

On Apr 18, 2013, at 2:15 PM, Michael Lueck mlu...@lueckdatasystems.com wrote:

 David Ashley wrote:
 You might try marking the rexxapi program as a sudo application and see
 if that fixes the problem.
 
 Without root/sudo perms to the share hosting server, I doubt I can accomplish 
 this. Am I correct?
 
 Disappointed indeed... :-(
 
 Sincerely,
 
 -- 
 Michael Lueck
 Lueck Data Systems
 http://www.lueckdatasystems.com/
 
 --
 Precog is a next-generation analytics platform capable of advanced
 analytics on semi-structured data. The platform includes APIs for building
 apps and a phenomenal toolset for data science. Developers can use
 our toolset for easy data analysis  visualization. Get a free account!
 http://www2.precog.com/precogplatform/slashdotnewsletter
 ___
 Oorexx-devel mailing list
 Oorexx-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/oorexx-devel

--
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis  visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


Re: [Oorexx-devel] Any progress on non-root perms an ooRexx 4.x?

2013-04-18 Thread René Jansen
Any port above 1024 can be used (opened, written to) by non-root users. The PID 
file location is the problem.

René.

On 18 apr. 2013, at 23:47, Mark Miesfeld miesf...@gmail.com wrote:

 On Thu, Apr 18, 2013 at 2:36 PM, CVBruce cvbr...@gmail.com wrote:
  
 I may be wrong, but I thought that root was only required if the port was 
 below a certain number, perhaps 1000.  Anything over this number could be 
 opened by ordinary users.  Did I remember this incorrectly, or has this 
 changed.
 
 Bruce, 
 
 I think that is correct, but I'm not 100% sure.
 
 Michael, 
 
 As I recall the real problem is that the rxapi code is written such that the 
 pid for the process is written to a directory that only root can write to.  
 If rxapi is installed as a system service than this is not problem for any 
 user running ooRexx.  But, it requires root access to get it installed to 
 begin with.  
 
 That explanation may not 100% technically correct, but it essentially 
 describes the problem.
 
 There should be some way to change the code so that an ordinary user can 
 install a private version of ooRexx that only runs for that user.  This then 
 may not comply 100% with Debian policy, or Fedora policy, or whatever policy. 
  But, I haven't made any effort to look into that.
 
 --
 Mark Miesfeld
 
 --
 Precog is a next-generation analytics platform capable of advanced
 analytics on semi-structured data. The platform includes APIs for building
 apps and a phenomenal toolset for data science. Developers can use
 our toolset for easy data analysis  visualization. Get a free account!
 http://www2.precog.com/precogplatform/slashdotnewsletter___
 Oorexx-devel mailing list
 Oorexx-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/oorexx-devel

--
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis  visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel