Re: Allow pidfile(3) to create pidfiles in arbitrary locations

[David Laight <david%l8s.co.uk@localhost>]

On Tue, Mar 29, 2011 at 09:26:01AM +0100, Julio Merino wrote:
> 
> On a second thought, I have updated the change to consider paths with an
> explicit '.pid' extension to be considered relative.  Otherwise, I'd expect
> confusion if the value to pidfile(3) was provided blindly from a
> user-provided parameter (like in foo -p foo.pid) and the pid file was created
> in /var/run.  The "only" way to get the old behavior is to just provide a
> basename (e.g. foo -p foo).

Probably be better to assume /var/run unless the filename contains a '/'.
So you'd need -p ./foo.pid to get a file in the current directory.

        David

-- 
David Laight: david%l8s.co.uk@localhost