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 451842 - qpidd init script doesn't deal well with errors in options file
Summary: qpidd init script doesn't deal well with errors in options file
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 1.0
Hardware: All
OS: Linux
Target Milestone: 1.3
: ---
Assignee: Gordon Sim
QA Contact: MRG Quality Engineering
Depends On:
TreeView+ depends on / blocked
Reported: 2008-06-17 18:58 UTC by Jeff Needle
Modified: 2010-04-29 13:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-04-29 13:36:56 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Jeff Needle 2008-06-17 18:58:36 UTC
I accidentally created /etc/sysconfig/qpidd with the following:


Yes, yes, I know.  You're supposed to quote the arguments.  But I didn't.  And
it leads to quite fun behavior.  Try it at home!  Just add the above line and
try a 'service qpidd stop' or 'service qpidd start', sit back, and watch.

RHEL4, RHEL5, doesn't matter.  This is fun for everyone.


Comment 2 Gordon Sim 2010-04-29 13:14:35 UTC
This isn't specific to qpid in that the same contents for the sysconfig file of any other service will cause the same effects. By sourcing the file we are executing it as a script and in this case that involves running the 'yes' command with strange effects.

I accept that this is a mistake more likely to be made for qpidd given the common use of yes as a value for options, but I don't see how we can avoid it. My suggestion would be to close this as WONT-FIX. Thoughts?

Comment 3 Gordon Sim 2010-04-29 13:36:56 UTC
After discussion with Jeff we agreed to close this as it is not directly a qpidd issue.

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