What would the correct way be to handle a program with a PID file being built to a prefix directory?

2014-06-18 Thread Michael Lueck
Greetings, What would the correct way be to handle a program with a PID file being built to a prefix directory? That is to say: Prefix, building the program with non root permissions to be run in the context of a user's home directory. PID file, generally defaults to /var/run, however in

Re: What would the correct way be to handle a program with a PID file being built to a prefix directory?

2014-06-18 Thread Gavin Smith
On Wed, Jun 18, 2014 at 3:47 AM, Michael Lueck mlu...@lueckdatasystems.com wrote: Prefix, building the program with non root permissions to be run in the context of a user's home directory. PID file, generally defaults to /var/run, however in this case permissions are not granted to /var/run.

Re: What would the correct way be to handle a program with a PID file being built to a prefix directory?

2014-06-18 Thread Eric Blake
On 06/18/2014 08:19 AM, Gavin Smith wrote: On Wed, Jun 18, 2014 at 3:47 AM, Michael Lueck mlu...@lueckdatasystems.com wrote: Prefix, building the program with non root permissions to be run in the context of a user's home directory. PID file, generally defaults to /var/run, however in this

Re: What would the correct way be to handle a program with a PID file being built to a prefix directory?

2014-06-18 Thread Michael Lueck
Greetings Gavin and Eric, So with the present stable autoconf localstatedir would be the build variable to interrogate, correct? Interrogate in order to select the correct logic path when building the PID file fully qualified filespec. Or would it be safe to just append the ${localstatedir} to