Yes, I found this out by reading all the /etc/rc* scripts after posting the message. Thanks for the confirmation, though. On Fri, 24 Oct 2003, Hugh E Cruickshank wrote: > Hi Michael: > > The problem is that the shutdown process needs some confirmation > that the process is actually running. What RH does is check for > a file of the same name as your script in the /var/lock/subsys/ > directory before it will execute the shutdown script. > > What I did was add a simple touch statement to our startup > script to create the file. In our case our startup/shutdown > script is "fa4srv" which calls "fa4dbstart" and "fa4dbstop" > to start/stop our database servers. I added: > > touch /var/lock/subsys/fa4srv > > to our "fa4dbstart" script and that resolved the problem. By > adding it to the "fa4dbstart" script rather than the "fa4srv" > script the shutdown will also work if we manually start the > servers. > > Credit for identifying this should go to Brian Ashe who helped me > with it last year. > > HTH > > Regards, Hugh > > -- > Hugh E Cruickshank, Forward Software, www.forward-software.com > > From: Michael Orr Sent: Friday, October 24, 2003 08:18 > > > > I have seen this question posted several times on NGs, but no responses. > > I have a RH2.1AS system upon which is installed an Oracle DB. I have a > > startup/shutdown script set to run via 'chkconfig'. All symlinks > > are in the > > proper places, and the script works perfectly during startup. > > The shutdown > > script works when called explicitly, but does not run when the > > system shuts > > down or reboots. It has a message in it to be displayed on > > shutdown, which > > isn't being displayed, so I know the script itself is not being > > called. Any > > ideas? > > > -- F. Michael Orr Computer Systems Sr. Engineer Virginia Community College System -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
