Bug 962263

Summary:	remove config reloading support from beaker
Product:	[Retired] Beaker	Reporter:	Dan Callaghan <dcallagh>
Component:	scheduler	Assignee:	beaker-dev-list
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.12	CC:	aigao, asaha, dcallagh, llim, qwan, rmancy
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	ImplementationQuality
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-19 23:12:43 UTC	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:

Description Dan Callaghan 2013-05-13 03:31:16 UTC

On SIGHUP beakerd reloads its configuration. This support was originally added at a time when beakerd wasn't rotating its own logs, and it didn't shut itself down cleanly (threads were killed in the middle of processing recipes).

Now that those reasons no longer apply, we should remove the reload support because it causes a lot of extra complexity, particularly in dealing with logging configuration.

See http://gerrit.beaker-project.org/1647 for some discussion.

Comment 1 Dan Callaghan 2013-09-19 23:12:43 UTC

SIGHUP handling was removed as part of bug 963542, released with Beaker 0.14.