Bug 232531

Summary: dbora not running when it is enabled as a K-script
Product: Red Hat Enterprise Linux 4 Reporter: Kurt Heine <kheine7>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED NOTABUG QA Contact: Brock Organ <borgan>
Severity: high Docs Contact:
Priority: medium    
Version: 4.3CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-03-16 00:27:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
initscript for oracle (dbora) none

Description Kurt Heine 2007-03-16 00:10:27 UTC 
Description of problem:
When I change run levels I have an oracle initscript which seems to work when it
is in startup mode (S91dbora) but when I change to a different runlevel where it
should be shutting down (K19dbora) it does not run the initscript.

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

How reproducible:
change from runlevel 3 to runlevel 2

Steps to Reproduce:
1. init 2
2.
3.
  
Actual results:
It seems to ignore this script (and there are other instances of this as well),
and just do some K-scripts but no others.

Expected results:
Databases should be shutdown.

Additional info:
I have chkconfig --del gpm and copied the gpm script to dbora and then chkconfig
--add dbora and used this and it suffers from the same problem.  Any time it
seems to execute the K-scripts it doesnt seem to know this exists (no message on
the screen about shutting down service).
Comment 1 Kurt Heine 2007-03-16 00:10:27 UTC 
Created attachment 150184 [details]
initscript for oracle (dbora)
Comment 2 Kurt Heine 2007-03-16 00:15:03 UTC 
initscripts version is 7.93.24.EL-1.1
Comment 3 Bill Nottingham 2007-03-16 00:27:15 UTC 
You don't touch a lock file in /var/lock/subsys that matches the script name
when you start, so it is not recorded as actually started. See some of the other
init scripts for examples.
Comment 4 Kurt Heine 2007-03-16 01:06:16 UTC 
OK figured out the problem.

I need to add a file into the /var/lock/subsys/<scriptname> (and delete) it
before changing runlevels will execute the script on shutdown.  As I have never
seen this before it would be nice to document this somewhere as it was only
through trial and error that I finally figured it out.