Re: [Oorexx-devel] Any progress on non-root perms an ooRexx 4.x?
Looking around a little bit on the Internet, I stumbled over: http://superuser.com/questions/454449/linux-alternative-places-where-to-store-pid-file-instead-of-var-run where one posting says: *In short*: you could store it anywhere (say, |/tmp| or |/var/tmp|), but |/var/run| is the preferred standard. |/var/run| is the Filesystem Hierarchy Standard http://www.pathname.com/fhs/2.2/fhs-5.13.html: This directory contains system information data describing the system since it was booted. Files under this directory must be cleared (removed or truncated as appropriate) at the beginning of the boot process. Programs may have a subdirectory of /var/run; this is encouraged for programs that use more than one run-time file.[footnote 37] And a desirable feature is that most distros clean it automatically http://stackoverflow.com/questions/5173636/must-my-pidfile-be-located-in-var-run (unlike |/tmp| which is not cleaned upon boot in some distros) - this avoid stale pid files: The normal location for pidfiles is /var/run. Most unices will clean this directory on boot; under Ubuntu this is achieved by /var/run an in-memory filesystem (tmpfs). It's your choice where to store it, but I would go with the standard. If you don't have access to |/var/run|, you should store the pid file in the user's home directory, e.g. |~/.my_app.pid|. So it seems, that it should be possible to differentiate between two use-cases, thereby possibly allowing ooRexx to run from a stick (without an installation with root permissions): * the ooRexx installer will need root privilegs and create whatever it needs (e.g. in /var/run) :), * if ooRexx is started up and there is no rxapi running and no directory in /var/run, then it would place the pid file in the user's home directory ~ as described above. This would allow ooRexx to be executable via a stick and without an explicit installation, which would ease tremendeously deployment of ooRexx in certain use (and show) cases! ---rony On 19.04.2013 22:05, CVBruce wrote: That's the issue. The user doesn't have root authority. Not to install or use ooRexx. Sent from an undisclosed location. On Apr 19, 2013, at 12:58 PM, Manfred Lotz manfred.l...@web.de wrote: On Fri, 19 Apr 2013 12:34:31 -0700 CVBruce cvbr...@gmail.com wrote: Well except you need root authority to create user lightdm and the directory in /var/run. Exactly. But this happens during installation of a package (running yum, apt-get or whatever installation program...) which always require root authority. -- Manfred -- 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?
Mark Miesfeld wrote: Change the code to this: *#undef* RUN_AS_DAEMON #ifdef RUN_AS_DAEMON #define OOREXX_PIDFILE /var/run/ooRexx.pid bool run_as_daemon = true; #else #define OOREXX_PIDFILE /*your_home_directory*/ooRexx.pid bool run_as_daemon = *true*; #endif Then rebuild and install to a directory you have write and execute privileges. Without testing, I believe that should work. Aaaahhh, so that is why for AIX there was the mkdir /var/run instruction. I think I will use the same directory that the prefix is configured to, and mkdir /var/run within that prefix structure. If you have problems, you're on your own. Oh but you are all coming up with such creative techniques... how could I not continue this thread to its successful completion! ;-) Thank you very much! You have certainly encouraged me. Oh... so if this does work... then could the configure with prefix command update this file on behalf of the person compiling and take care of making the directory? 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?
Greetings, I started with a fresh unpack of the source code I made the suggested changes Oh, and I removed path references to oorexx, then logged in and insured that export | grep oorexx returned nothing make blows up here: mv -f .deps/librexx_la-CallbackDispatcher.Tpo .deps/librexx_la-CallbackDispatcher.Plo /bin/sh ./libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -DORX_VER=4 -DORX_REL=1 -DORX_MOD=2 -DORX_FIX=0 -DORX_SYS_STR=\LINUX\ -DORX_CATDIR=\/kunden/homepages/35/d157794216/htdocs/opt/oorexx/bin\ -DORX_SHARED_LIBRARY_EXT=\.so\ -I./lib -I./api -I./api/platform/unix -I./common -I./common/platform/unix -I./interpreter -I./interpreter/behaviour -I./interpreter/execution -I./interpreter/memory -I./interpreter/package -I./interpreter/concurrency -I./interpreter/expression -I./interpreter/instructions -I./interpreter/classes -I./interpreter/classes/support -I./interpreter/runtime -I./interpreter/parser -I./interpreter/messages -I./interpreter/streamLibrary -I./interpreter/platform/common -I./interpreter/platform/unix -g -O2 -g -O2 -Wall -funsigned-char -Wpointer-arith -Wcast-qual -Wcast-align -Wshadow -Wwrite-strings -D__cplusplus -Wredundant-decls -DNOOPT -DPTHREAD_KERNEL -D_POSIX_THREAD -D_REENTRANT -D_GNU_SOURCE -DLINUX -DOPSYS_LINUX -MT librexx_la-TrappingDispatcher.lo -MD -MP -MF .deps/librexx_la-TrappingDispatcher.Tpo -c -o librexx_la-TrappingDispatcher.lo `test -f './interpreter/concurrency/TrappingDispatcher.cpp' || echo './'`./interpreter/concurrency/TrappingDispatcher.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -DORX_VER=4 -DORX_REL=1 -DORX_MOD=2 -DORX_FIX=0 -DORX_SYS_STR=\LINUX\ -DORX_CATDIR=\/kunden/homepages/35/d157794216/htdocs/opt/oorexx/bin\ -DORX_SHARED_LIBRARY_EXT=\.so\ -I./lib -I./api -I./api/platform/unix -I./common -I./common/platform/unix -I./interpreter -I./interpreter/behaviour -I./interpreter/execution -I./interpreter/memory -I./interpreter/package -I./interpreter/concurrency -I./interpreter/expression -I./interpreter/instructions -I./interpreter/classes -I./interpreter/classes/support -I./interpreter/runtime -I./interpreter/parser -I./interpreter/messages -I./interpreter/streamLibrary -I./interpreter/platform/common -I./interpreter/platform/unix -g -O2 -g -O2 -Wall -funsigned-char -Wpointer-arith -Wcast-qual -Wcast-align -Wshadow -Wwrite-strings -D__cplusplus -Wredundant-decls -DNOOPT -DPTHREAD_KERNEL -D_POSIX_THREAD -D_REENTRANT -D_GNU_SOURCE -DLINUX -DOPSYS_LINUX -MT librexx_la-TrappingDispatcher.lo -MD -MP -MF .deps/librexx_la-TrappingDispatcher.Tpo -c ./interpreter/concurrency/TrappingDispatcher.cpp -fPIC -DPIC -o .libs/librexx_la-TrappingDispatcher.o ./libtool: line 1130: 29710 Killed g++ -DHAVE_CONFIG_H -I. -DORX_VER=4 -DORX_REL=1 -DORX_MOD=2 -DORX_FIX=0 -DORX_SYS_STR=\LINUX\ -DORX_CATDIR=\/kunden/homepages/35/d157794216/htdocs/opt/oorexx/bin\ -DORX_SHARED_LIBRARY_EXT=\.so\ -I./lib -I./api -I./api/platform/unix -I./common -I./common/platform/unix -I./interpreter -I./interpreter/behaviour -I./interpreter/execution -I./interpreter/memory -I./interpreter/package -I./interpreter/concurrency -I./interpreter/expression -I./interpreter/instructions -I./interpreter/classes -I./interpreter/classes/support -I./interpreter/runtime -I./interpreter/parser -I./interpreter/messages -I./interpreter/streamLibrary -I./interpreter/platform/common -I./interpreter/platform/unix -g -O2 -g -O2 -Wall -funsigned-char -Wpointer-arith -Wcast-qual -Wcast-align -Wshadow -Wwrite-strings -D__cplusplus -Wredundant-decls -DNOOPT -DPTHREAD_KERNEL -D_POSIX_THREAD -D_REENTRANT -D_GNU_SOURCE -DLINUX -DOPSYS_LINUX -MT librexx_la-TrappingDispatcher.lo -MD -MP -MF .deps/librexx_la-TrappingDispatcher.Tpo -c ./interpreter/concurrency/TrappingDispatcher.cpp -fPIC -DPIC -o .libs/librexx_la-TrappingDispatcher.o make: *** [librexx_la-TrappingDispatcher.lo] Error 1 Changes to the source code were as follows: // For testing purposes comment out the following line to force RXAPI to // run as a foreground process. #define 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 = false; #endif APIServer apiServer; // the real server instance Configure command was: ./configure --disable-static --prefix=/kunden/homepages/35/d157794216/htdocs/opt/oorexx Suggestions? What exactly was having it select the logic path not to run as daemon? The usual way would be to run as daemon, correct? Obviously with the LOC I changed, since it now blows up I would think that is the logic path which was selected... I just do not understand why that path would be selected based on my running the standard build
Re: [Oorexx-devel] Any progress on non-root perms an ooRexx 4.x?
Michael Lueck wrote: Greetings, I started with a fresh unpack of the source code I made the suggested changes Oh, and I removed path references to oorexx, then logged in and insured that export | grep oorexx returned nothing make blows up here: Oh... I see there were a few more edits in that area other than just supplying the path. I will start over in that case. BRB... 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?
Greetings ooRexx developers, I will allow ooRexx to speak for itself... (uiserver):u40009095:~ which rexx /kunden/homepages/35/d157794216/htdocs/opt/oorexx/bin/rexx (uiserver):u40009095:~ rexx -v Open Object Rexx Version 4.1.2 Build date: Apr 20 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 (uiserver):u40009095:~ rexxtry.rex REXX-ooRexx_4.1.2(MT) 6.03 20 Apr 2013 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few...Enter 'exit' to end. say 'Yes, it works! Thank you, Mark! :-)' Yes, it works! Thank you, Mark! :-) ... rexxtry.rex on LINUX exit Customized ooRexx source code: // 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 Installation steps as follows: Version: ooRexx-4.1.2.source.tar.gz % ./configure --disable-static --prefix=/kunden/homepages/35/d157794216/htdocs/opt/oorexx % make % make install mkdir ~/opt/oorexx/var mkdir ~/opt/oorexx/var/run Symlinks for ooRexx 4.1.2 as follows: Add a symlink to support libraries compiled against the old ORexx 2.x from IBM ~/opt/oorexx/lib/ooRexx ln -s librexxapi.so.4.0.4 librexxapi.so.2 Add rexxtry.rex support from the command line ~/opt/oorexx/bin ln -s ../share/ooRexx/rexxtry.rex rexxtry.rex And put the proper shebang in that target file Thank you OOO much, Mark! The combined input from everyone is very appreciated. 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?
On Fri, 19 Apr 2013 13:05:18 -0700 CVBruce cvbr...@gmail.com wrote: That's the issue. The user doesn't have root authority. Not to install or use ooRexx. I don't understand what you are after. On a Linux system a software will be installed by an administrator who surely does have root authority. This is the way it works on *nix systems in general. If you happen to install a software privately then you won't have any package (let it be rpm or deb or whatever) but you would build the software manually (configure --prefix=..., make, make install) specifying a directory during configure (you are the owner of) where you install the software into. Let us assume I would install oorexx in /home/manfred/oorexx. Then the installation procedure should create a directory say /home/manfred/oorexx/var/run/oorexx where the rxapi pid file should go to. So where is the problem? -- Manfred -- 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?
Greetings Manfred, Manfred Lotz wrote: I don't understand what you are after. On a Linux system a software will be installed by an administrator who surely does have root authority. This is the way it works on *nix systems in general. The configure process supports the keyword prefix to target different root directory than the actual system root directory. This is helpful in being able to build without root perms software which will only work within the context of what user account on the shared Linux system. 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?
On 20.04.2013 17:46, Manfred Lotz wrote: On Fri, 19 Apr 2013 13:05:18 -0700 CVBruce cvbr...@gmail.com wrote: That's the issue. The user doesn't have root authority. Not to install or use ooRexx. I don't understand what you are after. On a Linux system a software will be installed by an administrator who surely does have root authority. This is the way it works on *nix systems in general. If you happen to install a software privately then you won't have any package (let it be rpm or deb or whatever) but you would build the software manually (configure --prefix=..., make, make install) specifying a directory during configure (you are the owner of) where you install the software into. Let us assume I would install oorexx in /home/manfred/oorexx. Then the installation procedure should create a directory say /home/manfred/oorexx/var/run/oorexx where the rxapi pid file should go to. So where is the problem? There are different kinds. - One problem is assuming that you have total control (root permissions) on the Unix box you use. If you do not have those rights, but wish to run rexx under your user account, then currently this is not possible as ooRexx demands root permissions. - Another use case is to experiment/test rexx without installing it, on one of your own machines, but also on friend's/collegue's boxes, maybe ones where they do not have root privileges. - Another use case are portable apps on a stick, where you plug in the stick in a box, that is not yours and you wish to run a set of applications that are important for you (e.g. utilities written in rexx) right from the stick. Whatever the use case, if ooRexx supported both out of the box, installation needing root permissions and running rexx without any installations, then the entire universe of ooRexx users/programmers is served. It seems from this thread that this is very feasible. ---rony -- 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?
On Sat, 20 Apr 2013 18:06:50 +0200 Rony G. Flatscher rony.flatsc...@wu.ac.at wrote: On 20.04.2013 17:46, Manfred Lotz wrote: On Fri, 19 Apr 2013 13:05:18 -0700 CVBruce cvbr...@gmail.com wrote: That's the issue. The user doesn't have root authority. Not to install or use ooRexx. I don't understand what you are after. On a Linux system a software will be installed by an administrator who surely does have root authority. This is the way it works on *nix systems in general. If you happen to install a software privately then you won't have any package (let it be rpm or deb or whatever) but you would build the software manually (configure --prefix=..., make, make install) specifying a directory during configure (you are the owner of) where you install the software into. Let us assume I would install oorexx in /home/manfred/oorexx. Then the installation procedure should create a directory say /home/manfred/oorexx/var/run/oorexx where the rxapi pid file should go to. So where is the problem? There are different kinds. - One problem is assuming that you have total control (root permissions) on the Unix box you use. If you do not have those rights, but wish to run rexx under your user account, then currently this is not possible as ooRexx demands root permissions. - Another use case is to experiment/test rexx without installing it, on one of your own machines, but also on friend's/collegue's boxes, maybe ones where they do not have root privileges. - Another use case are portable apps on a stick, where you plug in the stick in a box, that is not yours and you wish to run a set of applications that are important for you (e.g. utilities written in rexx) right from the stick. Whatever the use case, if ooRexx supported both out of the box, installation needing root permissions and running rexx without any installations, then the entire universe of ooRexx users/programmers is served. It seems from this thread that this is very feasible. Exactly. ooRexx has to be configured in order to support those different use cases and all is fine. -- Manfred -- 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?
Hi Michael, On Sat, 20 Apr 2013 11:58:44 -0400 Michael Lueck mlu...@lueckdatasystems.com wrote: Greetings Manfred, Manfred Lotz wrote: I don't understand what you are after. On a Linux system a software will be installed by an administrator who surely does have root authority. This is the way it works on *nix systems in general. The configure process supports the keyword prefix to target different root directory than the actual system root directory. This is helpful in being able to build without root perms software which will only work within the context of what user account on the shared Linux system. You quote the part of my last post where I refer to system administration tasks requiring root authority but then you talk about configure process which is a different beast. When I install oorexx on my Fedora box using a package the command looks like this: sudo yum install oorexx You are right about configure, make, make install. But I described it in my previous post in order to show that for a private installation the pid file has to reside in the private directory tree. Basically my conclusion is that there is no problem with pid file if oorexx is configured properly. -- Manfred -- 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?
For example, you are using a commercial web hosting company, which will not install any software that is not on their list of supported software, and you have some Rexx cgi scripts you want to use. On Apr 20, 2013, at 9:06 AM, Rony G. Flatscher wrote: - Another use case are portable apps on a stick, where you plug in the stick in a box, that is not yours and you wish to run a set of applications that are important for you (e.g. utilities written in rexx) right from the stick. -- 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?
Greetings Mandred, Manfred Lotz wrote: But I described it in my previous post in order to show that for a private installation the pid file has to reside in the private directory tree. Basically my conclusion is that there is no problem with pid file if oorexx is configured properly. Quite possibly what Mark suggested and I am now testing proves that there is no problem with locating the pid file relative to the prefix supplied. As-is, the source code (that one file) was hard coded to assume a specific directory. Performing a prefix'ed / individual user build/install, then that source file would be in error. Time will tell if that is the only sharp spot to successfully building ooRexx based on a user's home directory via the prefix parameter. For now I am very hopeful. 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?
Greetings Bruce, CVBruce wrote: For example, you are using a commercial web hosting company, which will not install any software that is not on their list of supported software, and you have some Rexx cgi scripts you want to use. Yes, something like that. Only with our server, httpd runs on one node of the server cluster, and our ssh account lands in another node... running a completely different kernel version. (Kernel 2.4x on the httpd node, and Kernel 2.6x on the ssh node.) Thus we can not run ooRexx via CGI on our server. :-( 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?
Hi David, On Thu, 18 Apr 2013 15:46:44 -0500 David Ashley w.david.ash...@gmail.com wrote: 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. IMHO, this is only half true. If you want to open a server port which is a privileged port (port number 1024) then the program must be run by a superuser. If a program binds to a non privileged port then the program could be run by a normal 'John Doe' user. -- Manfred -- 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?
On 19.04.2013 00:32, René Jansen wrote: Any port above 1024 can be used (opened, written to) by non-root users. The PID file location is the problem. How do other programs on Unix/Linux solve this problem (the PID file), if they are started via USB sticks and the like without root permissions? ---rony -- 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?
Hi Rony, On Fri, 19 Apr 2013 17:50:51 +0200 Rony G. Flatscher rony.flatsc...@wu.ac.at wrote: On 19.04.2013 00:32, René Jansen wrote: Any port above 1024 can be used (opened, written to) by non-root users. The PID file location is the problem. How do other programs on Unix/Linux solve this problem (the PID file), if they are started via USB sticks and the like without root permissions? ---rony I have an example on my linux box where a program isn't root and starts a server. It works like this: lightdm is a display manager. When the lightdm package gets installed then a directory /var/run/lightdm will be created like this: drwxrwxr-x 5 lightdm lightdm 100 Apr 12 13:40 lightdm/ Now the lightdm server could run as user lightdm and has authority to put its pid file below /var/run/lightdm/ -- Manfred -- 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?
Well except you need root authority to create user lightdm and the directory in /var/run. Bruce On Apr 19, 2013, at 12:23 PM, Manfred Lotz wrote: Hi Rony, On Fri, 19 Apr 2013 17:50:51 +0200 Rony G. Flatscher rony.flatsc...@wu.ac.at wrote: On 19.04.2013 00:32, René Jansen wrote: Any port above 1024 can be used (opened, written to) by non-root users. The PID file location is the problem. How do other programs on Unix/Linux solve this problem (the PID file), if they are started via USB sticks and the like without root permissions? ---rony I have an example on my linux box where a program isn't root and starts a server. It works like this: lightdm is a display manager. When the lightdm package gets installed then a directory /var/run/lightdm will be created like this: drwxrwxr-x 5 lightdm lightdm 100 Apr 12 13:40 lightdm/ Now the lightdm server could run as user lightdm and has authority to put its pid file below /var/run/lightdm/ -- Manfred -- 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?
On Fri, 19 Apr 2013 12:34:31 -0700 CVBruce cvbr...@gmail.com wrote: Well except you need root authority to create user lightdm and the directory in /var/run. Exactly. But this happens during installation of a package (running yum, apt-get or whatever installation program...) which always require root authority. -- Manfred -- 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?
On Thu, Apr 18, 2013 at 2:15 PM, Michael Lueck mlu...@lueckdatasystems.comwrote: Without root/sudo perms to the share hosting server, I doubt I can accomplish this. Am I correct? Disappointed indeed... :-( Michael, If I were you, I'd do this: make clean Then locate the file: rexxapi\server\platform\unix\APIService.cpp Around line 70 is this code: #define RUN_AS_DAEMON #ifdef RUN_AS_DAEMON #define OOREXX_PIDFILE /var/run/ooRexx.pid bool run_as_daemon = true; #else #define OOREXX_PIDFILE /tmp/ooRexx.pid bool run_as_daemon = false; #endif Change the code to this: *#undef* RUN_AS_DAEMON #ifdef RUN_AS_DAEMON #define OOREXX_PIDFILE /var/run/ooRexx.pid bool run_as_daemon = true; #else #define OOREXX_PIDFILE /*your_home_directory*/ooRexx.pid bool run_as_daemon = *true*; #endif Then rebuild and install to a directory you have write and execute privileges. Without testing, I believe that should work. If you have problems, you're on your own. -- 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
Re: [Oorexx-devel] Any progress on non-root perms an ooRexx 4.x?
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?
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?
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?
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?
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
Re: [Oorexx-devel] Any progress on non-root perms an ooRexx 4.x?
Mark Miesfeld wrote: I'm having a hard time following your thinking here. ;-) Those 3 exports obviously do not work. How in the world could it be bad to skip doing the wrong thing, in favor of doing the correct thing? Why are you trying to compile with xlc_r to begin with? I was trying to read the instructions via my ssh connection to the server... it looked like those were the instructions to build on 32-bit systems. I get the impression I ended up at the spot for 32-bit AIX, however. To compile on Debian 6.0.7 according to cat /etc/debian_version, were any of those exports necessary? 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?
Greetings David, David Ashley wrote: Yes, it should work with the current stable source. Just remember that the prefix option goes on the ./configure command, not the make command. Looking over the instructions, I copy/paste from them below... (compiling on a 32-bit server) % export CC=xlc_r % export CXX=xlC_r % export LDFLAGS=-Wl,-brtl -Wl,-bmaxdata:0x8000 % ./configure --disable-static % make % make install % mkdir /var/run To the ./configure LOC I will add the prefix. What about the mkdir? Shall I mkdir within my prefix fakeroot then? 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?
Yes. Add --prefix=fakeroot to the configure command. David Ashley On Fri, 2013-04-12 at 06:47 -0400, Michael Lueck wrote: Greetings David, David Ashley wrote: Yes, it should work with the current stable source. Just remember that the prefix option goes on the ./configure command, not the make command. Looking over the instructions, I copy/paste from them below... (compiling on a 32-bit server) % export CC=xlc_r % export CXX=xlC_r % export LDFLAGS=-Wl,-brtl -Wl,-bmaxdata:0x8000 % ./configure --disable-static % make % make install % mkdir /var/run To the ./configure LOC I will add the prefix. What about the mkdir? Shall I mkdir within my prefix fakeroot then? 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?
Actually I was asking about this step... David Ashley wrote: % mkdir /var/run What about the mkdir? Shall I mkdir within my prefix fakeroot then? -- 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?
I went ahead and tested the water of compiling on our present server. Last time
I build ooRexx was for v3.2.
I get an error:
(uiserver):u40009095:~ cd ~/build/ooRexx-4.1.2
(uiserver):u40009095:~/build/ooRexx-4.1.2 export CC=xlc_r
(uiserver):u40009095:~/build/ooRexx-4.1.2 export CXX=xlC_r
(uiserver):u40009095:~/build/ooRexx-4.1.2 export LDFLAGS=-Wl,-brtl
-Wl,-bmaxdata:0x8000
(uiserver):u40009095:~/build/ooRexx-4.1.2 ./configure --disable-static
--prefix=/kunden/homepages/35/d157794216/htdocs/opt/oorexx
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... xlc_r
checking whether the C compiler works... no
configure: error: in
`/kunden/homepages/35/d157794216/htdocs/build/ooRexx-4.1.2':
configure: error: C compiler cannot create executables
See `config.log' for more details
It looks like gcc is actually installed still.
(uiserver):u40009095:~ which gcc
/usr/bin/gcc
(uiserver):u40009095:~ which cpp
/usr/bin/cpp
The generated config.log is attached.
Suggestions? TIA!
--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by oorexx configure 4.1.2, which was
generated by GNU Autoconf 2.68. Invocation command line was
$ ./configure --disable-static
--prefix=/kunden/homepages/35/d157794216/htdocs/opt/oorexx
## - ##
## Platform. ##
## - ##
hostname = icpu2799
uname -m = i686
uname -r = 2.6.28.8-20120713a-iscsi-ntacker-3ware-sec8-fmon-igb-dif2-grsec
uname -s = Linux
uname -v = #1 SMP Fri Jul 13 13:37:07 CEST 2012
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /kunden/homepages/35/d157794216/htdocs/bin
PATH: /usr/local/bin
PATH: /usr/bin
PATH: /usr/X11R6/bin
PATH: /bin
PATH: /usr/local/msql/bin
PATH: /usr/games
PATH: .
PATH: /kunden/homepages/35/d157794216/htdocs/bin
PATH: /kunden/homepages/35/d157794216/htdocs/oorexx/bin
PATH: /kunden/homepages/35/d157794216/htdocs/drush
## --- ##
## Core tests. ##
## --- ##
configure:2381: checking build system type
configure:2395: result: i686-pc-linux-gnu
configure:2415: checking host system type
configure:2428: result: i686-pc-linux-gnu
configure:2448: checking target system type
configure:2461: result: i686-pc-linux-gnu
configure:2505: checking for a BSD-compatible install
configure:2573: result: /usr/bin/install -c
configure:2584: checking whether build environment is sane
configure:2634: result: yes
configure:2775: checking for a thread-safe mkdir -p
configure:2814: result: /bin/mkdir -p
configure:2827: checking for gawk
configure:2843: found /usr/bin/gawk
configure:2854: result: gawk
configure:2865: checking whether make sets $(MAKE)
configure:2887: result: yes
configure:3019: checking for gcc
configure:3046: result: xlc_r
configure:3275: checking for C compiler version
configure:3284: xlc_r --version 5
./configure: line 3286: xlc_r: command not found
configure:3295: $? = 127
configure:3284: xlc_r -v 5
./configure: line 3286: xlc_r: command not found
configure:3295: $? = 127
configure:3284: xlc_r -V 5
./configure: line 3286: xlc_r: command not found
configure:3295: $? = 127
configure:3284: xlc_r -qversion 5
./configure: line 3286: xlc_r: command not found
configure:3295: $? = 127
configure:3315: checking whether the C compiler works
configure:3337: xlc_r -Wl,-brtl -Wl,-bmaxdata:0x8000 conftest.c 5
./configure: line 3339: xlc_r: command not found
configure:3341: $? = 127
configure:3379: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME oorexx
| #define PACKAGE_TARNAME oorexx
| #define PACKAGE_VERSION 4.1.2
| #define PACKAGE_STRING oorexx 4.1.2
| #define PACKAGE_BUGREPORT
| #define PACKAGE_URL
| #define PACKAGE ooRexx
| #define VERSION 4.1.2
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:3384: error: in
`/kunden/homepages/35/d157794216/htdocs/build/ooRexx-4.1.2':
configure:3386: error: C compiler cannot create executables
See `config.log' for more details
## ##
## Cache variables. ##
## ##
ac_cv_build=i686-pc-linux-gnu
ac_cv_env_CCC_set=
ac_cv_env_CCC_value=
ac_cv_env_CC_set=set
ac_cv_env_CC_value=xlc_r
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXCPP_set=
Re: [Oorexx-devel] Any progress on non-root perms an ooRexx 4.x?
On Fri, Apr 12, 2013 at 8:13 PM, Michael Lueck mlu...@lueckdatasystems.comwrote: I went ahead and tested the water of compiling on our present server. Last time I build ooRexx was for v3.2. I get an error: (uiserver):u40009095:~ cd ~/build/ooRexx-4.1.2 (uiserver):u40009095:~/build/**ooRexx-4.1.2 export CC=xlc_r (uiserver):u40009095:~/build/**ooRexx-4.1.2 export CXX=xlC_r Are you actually on an AIX machine? ... checking for gcc... xlc_r checking whether the C compiler works... no configure: error: in `/kunden/homepages/35/**d157794216/htdocs/build/** ooRexx-4.1.2': configure: error: C compiler cannot create executables See `config.log' for more details It looks like gcc is actually installed still. (uiserver):u40009095:~ which gcc /usr/bin/gcc That shows that gcc is installed. It says nothing about xlc_r If you are on a Linux machine, why don't you just compile with gcc, or g++? We know that works. Why throw xlc_r in the mix? -- 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
Re: [Oorexx-devel] Any progress on non-root perms an ooRexx 4.x?
Greetings, I found a work-around, as follows: 1) I logged back into SSH 2) I skipped these lines Michael Lueck wrote: (uiserver):u40009095:~/build/ooRexx-4.1.2 export CC=xlc_r (uiserver):u40009095:~/build/ooRexx-4.1.2 export CXX=xlC_r (uiserver):u40009095:~/build/ooRexx-4.1.2 export LDFLAGS=-Wl,-brtl -Wl,-bmaxdata:0x8000 And just ran these: (uiserver):u40009095:~ cd ~/build/ooRexx-4.1.2 (uiserver):u40009095:~/build/ooRexx-4.1.2 ./configure --disable-static --prefix=/kunden/homepages/35/d157794216/htdocs/opt/oorexx And then make / make install ./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 Woo hoo!!! :-) So, how bad is it that I did not do those three exports? 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?
On Fri, Apr 12, 2013 at 8:26 PM, Michael Lueck mlu...@lueckdatasystems.comwrote: I found a work-around, as follows: 1) I logged back into SSH 2) I skipped these lines Michael Lueck wrote: (uiserver):u40009095:~/build/ooRexx-4.1.2 export CC=xlc_r (uiserver):u40009095:~/build/ooRexx-4.1.2 export CXX=xlC_r (uiserver):u40009095:~/build/ooRexx-4.1.2 export LDFLAGS=-Wl,-brtl -Wl,-bmaxdata:0x8000 So, how bad is it that I did not do those three exports? Michael, I'm having a hard time following your thinking here. ;-) Those 3 exports obviously do not work. How in the world could it be bad to skip doing the wrong thing, in favor of doing the correct thing? Why are you trying to compile with xlc_r to begin with? -- 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
Re: [Oorexx-devel] Any progress on non-root perms an ooRexx 4.x?
Yes, it should work with the current stable source. Just remember that the prefix option goes on the ./configure command, not the make command. David Ashley On Tue, 2013-04-09 at 17:25 -0400, Michael Lueck wrote: 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. aaahhh, yes, I believe that is what I am doing. I am installing from source, not making a package. I need to compile ooRexx giving it the correct prefix location to install to. So you think that should already work with the current stable source tarball? 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?
Greetings David, David Ashley wrote: Yes, it should work with the current stable source. Just remember that the prefix option goes on the ./configure command, not the make command. Thank you for confirmation. I will report back with the results. 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?
At the moment, it might be easiest to explain what the root problem is and give you a way to work around it. First, this problem is only with RPM builds and does not occur in DEB builds. The reason for this is that the DEB builds are done under the fakeroot environment and that environment provides the correct default prefix. RPM builds are done under a standard userid and the prefix that get set for a standard user is /usr/local and not /usr. This is a big problem because /usr/local/bin is NOT in the default PATH for most RPM-based distributions. To correct this we supply our own --prefix option when building an RPM which is set to /usr. We could use fakeroot for the RPM builds but it is not installed by default on any distribution due to it being a security risk. So how do you work around this? Look at line 145 of the ./platform/unix/oorexx.spec.in file. There you will see where we override the prefix during the building of the RPM. Simply remove this option from the configure command and rebuild your RPM by rerunning the configure command with your own prefix and then doing the make rpm command. That will build an RPM with your custom prefix. You might think that we could install the fakeroot command onto the distribution and set a prereq on it and we would be done with this problem. But no, that will not work. If the RPM is then built as the root user the fakeroot command gives errors and the build will fail. That is why we have our workaround. I may do some experimenting this week with testing to see if we are the root user and then supplying the correct build options. I will let you know how this turns out. David Ashley On Sat, 2013-04-06 at 22:58 -0400, Michael Lueck wrote: Greetings, It has been some time since I brought the topic up last. For Linux shared hosting, we are stuck running ooRexx 3.2 as the highest version. On shared hosting, we do not have a root account to the server. Installed software requires the build process to support the prefix switch and to be compiled based on the home directory as the deployment target. Has there been any progress made at researching if by some creative work that restriction could be lifted again? I would very much like to maintain the latest ooRexx version across hosts, including shared hosting. 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?
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. David Ashley On Sat, 2013-04-06 at 22:58 -0400, Michael Lueck wrote: Greetings, It has been some time since I brought the topic up last. For Linux shared hosting, we are stuck running ooRexx 3.2 as the highest version. On shared hosting, we do not have a root account to the server. Installed software requires the build process to support the prefix switch and to be compiled based on the home directory as the deployment target. Has there been any progress made at researching if by some creative work that restriction could be lifted again? I would very much like to maintain the latest ooRexx version across hosts, including shared hosting. 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?
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. aaahhh, yes, I believe that is what I am doing. I am installing from source, not making a package. I need to compile ooRexx giving it the correct prefix location to install to. So you think that should already work with the current stable source tarball? 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?
To be honest, it has been some time since I looked into this. I will try to see what can be done this week. David Ashley On Sat, 2013-04-06 at 22:58 -0400, Michael Lueck wrote: Greetings, It has been some time since I brought the topic up last. For Linux shared hosting, we are stuck running ooRexx 3.2 as the highest version. On shared hosting, we do not have a root account to the server. Installed software requires the build process to support the prefix switch and to be compiled based on the home directory as the deployment target. Has there been any progress made at researching if by some creative work that restriction could be lifted again? I would very much like to maintain the latest ooRexx version across hosts, including shared hosting. Sincerely, -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
