could we, for the moment, just have an environment variable that overrides the default? Meaning that when it is not there, we write the PID to standard; when it is there, we write the PID where it indicates we want it to be. That should satisfy worries over changing this?
René. > On 21 Nov 2018, at 13:07, Michael Lueck <[email protected]> wrote: > > Greetings Rick, > > Rick McGuire wrote: >> It's not really that simple. I believe writing the pid file at that location >> is part of the requirements for running as a daemon on other unix-based >> systems. I wish David Ashley were still around, he did all of that work and >> would know the issues. > > > Ah yes, the PID file... I believe that is what I had to hack the path of in > the source code in order to build/compile to be run as a non-root user on > Linux. Correct? > > Did that ever get correctly resolved, that you can build/run ooRexx v5 with a > custom prefix directory, jailing it to the user's home directory? > > Yes yes, I am aware that the socket still gets opened in the context of the > entire machine, so only one user could run ooRexx at a time. I do not think > desiring to run ooRexx on Shared Web Hosting servers is common, sadly... not > concerned about that risk. > > I am thankful, > > -- > Michael Lueck > Lueck Data Systems > http://www.lueckdatasystems.com/ > > > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
