Description of problem:
The init scripts for beaker-proxy and beaker-watchdog do not create a PID file in /var/run.  They do create a lock file in /var/lock/subsys. 

Doing a service beaker-proxy status returns:
[root@lab-stage ~]# service beaker-proxy status
beaker-proxy dead but subsys locked
[root@lab-stage ~]#

Version-Release number of selected component (if applicable):
beaker-lab-controller-0.5.53-1.el5

How reproducible:
always

Steps to Reproduce:
1. service beaker-proxy start
2. service beaker-proxy status
  
Actual results:
[root@lab-stage ~]# service beaker-proxy status
beaker-proxy dead but subsys locked
[root@lab-stage ~]# 

Expected results:

[root@lab-stage ~]# service beaker-proxy status
beaker-proxy (pid xxx) is running
[root@lab-stage ~]#