Bug 451842

Summary:	qpidd init script doesn't deal well with errors in options file
Product:	Red Hat Enterprise MRG	Reporter:	Jeff Needle <jneedle>
Component:	qpid-cpp	Assignee:	Gordon Sim <gsim>
Status:	CLOSED WONTFIX	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	1.0	CC:	gsim
Target Milestone:	1.3
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-04-29 13:36:56 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-17 18:58:36 UTC

I accidentally created /etc/sysconfig/qpidd with the following:

QPIDD_OPTIONS=-m yes

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.

qpidd-0.2.667603-1

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.