Bug 711826 - rc.sysinit fails to remove lockfiles under /var/lock/subsys on bootup
Summary: rc.sysinit fails to remove lockfiles under /var/lock/subsys on bootup
Keywords:
Status: CLOSED DUPLICATE of bug 705236
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: initscripts
Version: 5.7
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: initscripts Maintenance Team
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-08 16:10 UTC by Bill Peck
Modified: 2011-06-09 12:27 UTC (History)
4 users (show)

Fixed In Version: initscripts-8.45.38-1.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-08 16:28:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Bill Peck 2011-06-08 16:10:44 UTC
Description of problem:

This is a very bad regression.  

If the system doesn't reboot cleanly (removing lockfiles on the way down) then on bootup the init process won't even attempt to start the service because the lockfile exists.

Normally rc.sysinit would delete these lockfiles on bootup, but this patch that was introduced between 5.6 and 5.7 keeps that from working.

 -849,6 +850,9 @@
 		*/dovecot)	rm -f $afile/* $afile/*/* ;;
 		*/cups)		rm -f $afile/*/* ;;
 		*/libvirt)	rm -rf $afile/*/* ;;
+		*/subsys)       if [ -d "$afile/rhsm" ]; then 
+					rm -rf $afile/rhsm/* 
+				fi ;;
 		*)		rm -f $afile/* ;;
 	   esac
 	else

Version-Release number of selected component (if applicable):
initscripts-8.45.36-1.el5

How reproducible:
Everytime

Steps to Reproduce:
1. Crash the system
2. not even sshd will start
3.


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