> -----Original Message----- > From: centos-bounces at centos.org > [mailto:centos-bounces at centos.org] On Behalf Of Robert Spangler > Sent: Sunday, December 05, 2010 10:51 AM > To: CentOS mailing list > Subject: Re: [CentOS] # chkconfig: kill at run level 3 > > On Friday 03 December 2010 19:30, Michael D. Berger wrote: > > > In the control script of my daemon in /etc/init.d?, I have > > # chkconfig: 35 97 3 > > > > The result of this is that I have links: > > /etc/rc.d/rc1.d/K03... > > /etc/rc.d/rc3.d/S97... > > /etc/rc.d/rc5.d/S97... > > > > As mentioned in a previous thread, my complex daemon throws an > > exception when I shutdown. Perhaps things might be better > if I had: > > /etc/rc.d/rc3.d/K03... The number after the S and K determine the order in which they're run. S01 starts things which S02-S99 might require; S02 might depend on S01 and provide service the S03-S99 stuff requires. And, so on. The K scripts *generally* follow the reverse order on the logic that nothing is shut down while something else might require it. Therefore a service with S01 has K99, what is S02 has K98, and so on. I'd (personally) guess at the Wild Blue that your Kxx kill script has a high enough number that it's shutting your app down after something else has been shut down, on which your app depends, without which your app throws an exception. That's why (guess based on previous guess) if you kill your app then shut down, everything is happy. General Rule of Thumb: Sxx -> K(100-xx) ******************************************************************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated**