Bug 451079 - qpidd service does no logging by default
qpidd service does no logging by default
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Alan Conway
Kim van der Riet
Depends On:
  Show dependency treegraph
Reported: 2008-06-12 13:47 EDT by Alan Conway
Modified: 2009-05-07 16:09 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-12-02 11:06:32 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alan Conway 2008-06-12 13:47:21 EDT
Description of problem:

When started as a service qpidd  does no logging by default.

Possible solutions:
 - release note it, explain how to enable in qpidd.conf with log-output=syslog
 - add log-output=syslog to default qpidd.conf
 - modify qpidd code so it logs to syslog by default if started in daemon mode,
to stderr oterwise.
Comment 1 Gordon Sim 2008-06-12 13:51:40 EDT
Or my own personal favourite: 
 - add --log-output syslog to the qpidd init script
Comment 2 Alan Conway 2008-06-12 15:08:59 EDT
Issues with some approaches.

 - add --log-output syslog to the qpidd init script

This over-rides the config file and makes it impossible to configure the
init-script launched qpidd NOT to log to syslog unless you edit the init script.  

 - add log-output=syslog to default /etc/qpidd.conf
This makes syslog and not stderr the default for everyone. Not developer friendly.
Comment 3 Alan Conway 2008-06-12 18:00:45 EDT
Fixed qpidd to default to syslog in --daemon mode.
Revision: 667253
Comment 4 Mike Bonnet 2008-06-19 23:53:41 EDT
qpidc-0.2.667603-1.el5, qpidc-perftest-0.2.667603-1.el5, qpidd-0.2.667603-1.el5, and rhm-0.2.2153-1.el5 have been pushed to the staging repo for testing

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