Bug 451695 - Docs suggest log-output=/var/log/qpidd.log but this isn't writeable by user qpidd
Docs suggest log-output=/var/log/qpidd.log but this isn't writeable by user q...
Status: CLOSED NEXTRELEASE
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Messaging_Installation_and_Configuration_Guide (Show other bugs)
1.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Lana Brindley
Kim van der Riet
: Documentation
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-16 14:40 EDT by Jeff Needle
Modified: 2013-10-23 19:08 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-08-14 01:19:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jeff Needle 2008-06-16 14:40:40 EDT
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 08:49:41 EDT
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 16:38:26 EDT
This bug is no longer an issue in that review copy.

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