Bug 451009 - confusion over pid file location when pid-dir == data-dir
Summary: confusion over pid file location when pid-dir == data-dir
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: beta
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: Kim van der Riet
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-12 11:33 UTC by Gordon Sim
Modified: 2021-03-16 12:47 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gordon Sim 2008-06-12 11:33:07 UTC
[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 12:58:05 UTC
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.