Bug 62495 - system startup does not clear locks in subsys dir
Summary: system startup does not clear locks in subsys dir
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 7.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-04-01 20:07 UTC by Need Real Name
Modified: 2014-03-17 02:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-04-01 20:11:49 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2002-04-01 20:07:18 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

Description of problem:
If the system crashes hard, then when the system starts up, some services 
refuse to start because they have locks set in the /var/lock/subsys directory.

Basically, need to mod rc.sysinit to clear that directory.  Maybe you could 
make a directory like /etc/sysinit-clear.d that contains symbolic links to 
directories to be cleared at system startup.  
That way, rpms could install their favorite directories there to be 
cleaned up.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.power-off running system
2.watch for subsystems that don't start OK
3.
	

Additional info:

Comment 1 Bill Nottingham 2002-04-01 20:11:44 UTC
From rc.sysinit:

for afile in /var/lock/* /var/run/*; do
   if [ -d "$afile" ]; then
      [ "`basename $afile`" != "news" -a "`basename $afile`" != "sudo" -a
"`basename $afile`" != "mon" ] && rm -f $afile/*
   else
      rm -f $afile
   fi
done

Does this not work for you?

Comment 2 Bill Nottingham 2002-11-25 22:00:38 UTC
closed, no response


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