Red Hat Bugzilla – Bug 451842
qpidd init script doesn't deal well with errors in options file
Last modified: 2010-04-29 09:36:56 EDT
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.
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?
After discussion with Jeff we agreed to close this as it is not directly a qpidd issue.