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:

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 (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):


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.lotz@web.de> wrote:

On Fri, 19 Apr 2013 12:34:31 -0700
CVBruce <cvbruce@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.