Solved

Shutdown problems...

Posted on 2004-04-30
2
322 Views
Last Modified: 2013-12-15
I have a system running RH AS 2.1 and I am having problems getting it to shut down cleanly due to an installed application that must be shutdown early.  

Our developers use ClearCase as their version control tool and if it's parent service (atria) doesn't get shutdown before other stuff it relies on (eg. amd, nfs, etc...) it causes a kernal panic during shutdown/reboot.  Normally, it's not an issue, we just run the install scripts and go on our merry way, but this system has forced me to re-install from scratch 3 times and I'm still stuck with the same problem.

I changed atria's kill number from the default of 35 to 2 in /etc/rc.d/rc6.d, but if I choose halt from the logon screen or do a shutdown/halt/reboot while logged in it appears to ignore the order of links in rc6.d .   Selecting reboot from from the logon screen works as expected and the system shuts down and reboots fine.

How do I affect the shutdown order for the other methods of shutting down the computer?  According to documentation, as I understand it,  shutdown/halt/reboot are supposed to be the same command and are supposed to switch the system to init level 6 which triggers the stopping of the various services by running the linked scripts.  Any thoughts or insights would be appreciated...
0
Comment
Question by:danm66
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 40

Accepted Solution

by:
jlevie earned 350 total points
ID: 10965014
If the system init scripts for ClearCase follow the standard for RedHat there'll be a line similar to:

# chkconfig: 2345 80 30

at the beginning of the script. This tell chkconfig what run levels the the service should be started in by default (i.e., chkconfig service on) and the precedence of the start/stop operations. When entering a run-level all K scripts are run and then all S scripts, in order of precedence.

Run levels 0, 1, & 6 are special. 6 is used only to prepare the system for and execute a reboot. Run level 1 is used to go to single user mode and 0 is used for halt. So, changing the precedence of the atria K script in run level 6 only affects a reboot. To change the precedence for a shtdown you'll need to change the precedence in 0 & 1
0
 
LVL 16

Author Comment

by:danm66
ID: 10991190
Ahhh!!!  The missing piece of the puzzle.  I knew what level 6 and, apparently, levels 2-5, but I didn't investigate 0 and 1.  Moving the atria kill links up in the 0 and 1 folders now allow it to shutdown without doing a kernal panic.  The curious part is why this system has this issue.  I'm sure that we've installed ClearCase on other systems running AS 2.1 without running into this issue.  Oh well, at least I can close this call and move on now.
Thanks for the help!!!
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Using 'screen' for session sharing, The Simple Edition Step 1: user starts session with command: screen Step 2: other user (logged in with same user account) connects with command: screen -x Done. Both users are connected to the same CLI sessio…
Google Drive is extremely cheap offsite storage, and it's even possible to get extra storage for free for two years.  You can use the free account 15GB, and if you have an Android device..when you install Google Drive for the first time it will give…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Learn how to navigate the file tree with the shell. Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question