Bug 451009 - confusion over pid file location when pid-dir == data-dir
confusion over pid file location when pid-dir == data-dir
Status: NEW
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
beta
All Linux
medium Severity low
: ---
: ---
Assigned To: Ted Ross
Kim van der Riet
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-12 07:33 EDT by Gordon Sim
Modified: 2013-02-24 08:23 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Gordon Sim 2008-06-12 07:33:07 EDT
[gordon@thinkpad cpp]$ ./src/qpidd  --pid-dir temp-data -d --data-dir temp-data
[gordon@thinkpad cpp]$ ./src/qpidd  --pid-dir temp-data -q --data-dir temp-data
Cannot open temp-data/qpidd.5672.pid: No such file or directory

If the pid-dir is specified it appears to need to be an absolute path(?).
However if you specify the same relative path for data-dir and pid-dir the
daemon starts but fails when shutdown (using the --quit option) as the pid file
is in an unexpected location. The data-dir above is actually in
temp-dir/temp-dir, and the pid is in the inner nested temp-dir.
Comment 1 Gordon Sim 2008-06-12 08:58:05 EDT
Workaround is just to always use absolute paths when using --daemon. Suggest we
just release note this to advise users to do so.

Note You need to log in before you can comment on or make changes to this bug.