Bug 451695

Summary: Docs suggest log-output=/var/log/qpidd.log but this isn't writeable by user qpidd
Product: Red Hat Enterprise MRG Reporter: Jeff Needle <jneedle>
Component: Messaging_Installation_and_Configuration_GuideAssignee: Lana Brindley <lbrindle>
Status: CLOSED NEXTRELEASE QA Contact: Kim van der Riet <kim.vdriet>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0CC: lbrindle, mhideo
Target Milestone: ---Keywords: Documentation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-08-14 05:19:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jeff Needle 2008-06-16 18:40:40 UTC
The Messaging Installation Guide, Chapter 3, section 2 suggests examples for
/etc/qpidd.conf including log-output=/var/log/qpidd.log.  This log file doesn't
exist, and user qpidd won't have the privileges to create it.  We should either
create it upon installation so user qpidd can write to it or change our docs. 
I'd recommend the former.  Also want to make sure that log rollover does the
right thing with respect to file ownership if we go in that direction.

If this is a docs change instead of a behavior change (i.e. direct people to use
/tmp or something), reassign to Lana.

Comment 1 Jeff Needle 2008-06-17 12:49:41 UTC
As Gordon pointed out to me, the default behavior for logging is to use syslog,
and that puts the messages in /var/log/messages.  We should just remove the
log-output= line from the example qpidd.conf file so as to not confuse people. 
If they want to explore the additional qpidd options, they can read the man page.

Comment 3 Jeff Needle 2008-07-17 20:38:26 UTC
This bug is no longer an issue in that review copy.