Bug 1174139

Summary:	rhqctl console does not handle signals correctly
Product:	[Other] RHQ Project	Reporter:	Michael Burman <miburman>
Component:	Launch Scripts	Assignee:	Nobody <nobody>
Status:	ON_QA ---	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.13	CC:	hrupp
Target Milestone:	---
Target Release:	RHQ 4.14
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1176162 (view as bug list)		Environment:
Last Closed:		Type:	Bug
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:
Bug Blocks:	972728, 1176162

Description Michael Burman 2014-12-15 08:59:55 UTC

Description of problem: rhqctl does not catch operating system signals such as sigterm correctly. This causes rhqctl console to behave incorrectly and leave console software running on the background.


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


How reproducible: Always.


Steps to Reproduce:
1.
2.
3.

Actual results: Only rhqctl dies from sigterm, not the software running on the console.


Expected results: sigterm should be sent to the underlying process also.


Additional info: These prevent some systemd / container / other supervisor support.

Comment 1 Michael Burman 2014-12-15 15:58:39 UTC

In PR #154

Comment 2 Michael Burman 2015-03-09 13:43:50 UTC

Some additional fixes to the master (this fixes rhq-agent.sh):

commit 48507acad70ba89e16b7c3cd7ad1aa4b888373a3
Author: Michael Burman <miburman>
Date:   Mon Mar 9 15:40:58 2015 +0200

    [BZ 1174139] Fix starting script to work with FreeBSD also (and possibly some other sh-variants)