Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 451009

Summary: confusion over pid file location when pid-dir == data-dir
Product: Red Hat Enterprise MRG Reporter: Gordon Sim <gsim>
Component: qpid-cppAssignee: Ted Ross <tross>
Status: NEW --- QA Contact: Kim van der Riet <kim.vdriet>
Severity: low Docs Contact:
Priority: medium    
Version: beta   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
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: --- Target Upstream Version:

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/ 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.