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

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.

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

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

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" wrote: > > On 20.04.2013 17:46, Manfred Lotz wrote: > > On Fri, 19 Apr 2013 13:05:18 -0700 > > CVBruce wrote: > > > >> That's the issue. The user doesn't have root authority. Not to > >> install or use ooRexx. > >> > > I don't understand

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

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 t

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

On Fri, 19 Apr 2013 13:05:18 -0700 CVBruce 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

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 Co

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 ed

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

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 "/**/ooRexx.pid" > bool run_as_daemon = *true*; > #endif > > > Then rebuild and install t

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

Looking around a little bit on the Internet, I stumbled over: where one posting says: *In short*: you could store it anywhere (say, |/tmp| or |/var/tmp|), but |/var/run| is the pref