Bug 962263 - remove config reloading support from beaker
Summary: remove config reloading support from beaker
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: 0.12
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact:
URL:
Whiteboard: ImplementationQuality
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-13 03:31 UTC by Dan Callaghan
Modified: 2018-02-06 00:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-19 23:12:43 UTC
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.