Bug 592250 - [FEATURE] qpid broker (qpidd) should better log his run configuration
Summary: [FEATURE] qpid broker (qpidd) should better log his run configuration
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp   
(Show other bugs)
Version: Development
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: mick
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Keywords: FutureFeature
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-14 11:09 UTC by Frantisek Reznicek
Modified: 2019-02-08 15:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
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)

Description Frantisek Reznicek 2010-05-14 11:09:22 UTC
Description of problem:

I believe that at least broker should have summarize in head of it's log what is the run configuration to be sure what parameters are given, what were taken from command-line what ones from config file and finally what are the defaults for params not specified.

The similar thing would be beneficial for all clients, at least for c++ clients.


Version-Release number of selected component (if applicable):
<= MRG 1.3

How reproducible:
N/A

Steps to Reproduce:
N/A
  
Actual results:
qpidd broker does not dump running configuration to it's log file.

Expected results:
qpidd broker should dump running configuration to it's log file.

Additional info:

I recall that Verilog-XL simulator had it done well.


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