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 454202 - qpidd should own /var/run/qpidd and set proper permissions
Summary: qpidd should own /var/run/qpidd and set proper permissions
Alias: None
Product: Fedora
Classification: Fedora
Component: qpidc
Version: 9
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Ted Ross
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-07-06 15:08 UTC by Ed Hill
Modified: 2009-07-15 08:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-07-15 08:14:55 UTC

Attachments (Terms of Use)

Description Ed Hill 2008-07-06 15:08:07 UTC
Description of problem:

$ /etc/init.d/qpidd start 
Starting Qpid AMQP daemon: Can't create PID directory: /var/run/qpidd
$ rpm -q --whatprovides /var/run/qpidd
file /var/run/qpidd is not owned by any package

Version-Release number of selected component (if applicable):

Additional info:

The qpidd package should own the /var/run/qpidd dir and should give it
permissions consistent with the qpidd user.

Comment 1 Ed Hill 2008-07-06 15:11:20 UTC
Hi there, I wanted to assign this bug to the "qpidd" package (and not the 
"qpidc" package) but bugzilla [in its infinite wisdom! ;-)] does not seem 
to have a "qpidd" package listed for F8.  Oh, well...

Also, if I create the directory:

  mkdir /var/run/qpidd
  chown qpidd:qpidd /var/run/qpidd

then I have no trouble starting/stopping/re-starting the qpidd service.

Comment 2 Nuno Santos 2008-07-07 17:07:59 UTC
This is now fixed in release -2 of the qpidd package, qpidd-0.2.667603-2.fc8,
which should be in the F8-updates repo in the next couple of days.

Comment 3 Bug Zapper 2009-06-10 01:56:51 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here:

Comment 4 Bug Zapper 2009-07-15 08:14:55 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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