Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 567366

Summary:	Update qpidd initscript to allow setting environment vars in sysconfig
Product:	Red Hat Enterprise MRG	Reporter:	Ken Giusti <kgiusti>
Component:	qpid-cpp	Assignee:	messaging-bugs <messaging-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.2	CC:	jross
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	567362	Environment:
Last Closed:	2013-03-21 23:04:18 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:
Bug Depends On:	564105, 567362
Bug Blocks:

Description Ken Giusti 2010-02-22 18:39:21 UTC

+++ This bug was initially created as a clone of Bug #567362 +++

Created an attachment (id=395531)
A modified version of the qpidd init script that allows env vars in sysconfig/qpidd

Description of problem:

We are unable to configure environment variables for qpidd via the sysconfig file.

Version-Release number of selected component (if applicable):


How reproducible:

100% 

Steps to Reproduce:
1.export SOMEVAR=SomeValue in qpidd's sysconfig file
2.cat /proc/<qpidd-pid>/environ file
3.SOMEVAR not set
  
Actual results:


Expected results:


Additional info:

A fix to the initscripts package is being made to allow a daemon's init script the option of passing environment variables to the daemon.  See BZ564093.  Once this fix is available, the qpidd init script /etc/init.d/qpidd -may- need to be updated to take advantage of this feature.

As a work around, the qpidd init script /etc/init.d/qpidd may be modified to avoid using the daemon() function.  See the attached example.

Comment 1 Justin Ross 2013-03-21 23:04:18 UTC

As far as I can tell, the original motivation for cloning this bug no longer holds. -> CLOSED(duplicate).

*** This bug has been marked as a duplicate of bug 567362 ***