Bug 232531 - dbora not running when it is enabled as a K-script
dbora not running when it is enabled as a K-script
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: initscripts (Show other bugs)
4.3
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-15 20:10 EDT by Kurt Heine
Modified: 2014-03-16 23:06 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-03-15 20:27:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
initscript for oracle (dbora) (2.05 KB, text/plain)
2007-03-15 20:10 EDT, Kurt Heine
no flags Details

  None (edit)
Description Kurt Heine 2007-03-15 20:10:27 EDT
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-15 20:10:27 EDT
Created attachment 150184 [details]
initscript for oracle (dbora)
Comment 2 Kurt Heine 2007-03-15 20:15:03 EDT
initscripts version is 7.93.24.EL-1.1
Comment 3 Bill Nottingham 2007-03-15 20:27:15 EDT
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-15 21:06:16 EDT
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.

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