Bug 812722 - beakerd init scripts do not check pidfile/process status before starting
Summary: beakerd init scripts do not check pidfile/process status before starting
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: 0.8
Hardware: Unspecified
OS: Unspecified
urgent
urgent vote
Target Milestone: ---
Assignee: Steven Lawrance
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-16 05:38 UTC by Steven Lawrance
Modified: 2019-05-22 13:42 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-14 00:09:47 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Steven Lawrance 2012-04-16 05:38:24 UTC 
Before starting (or restarting) beakerd, the init scripts should check whether stale pidfiles (or lockfiles) exist and if so, either remove them or refuse to start.
Comment 1 Dan Callaghan 2012-08-14 00:09:47 UTC 
This was fixed in beaker-server-0.8.2-3.
Note You need to log in before you can comment on or make changes to this bug.