Results 1 to 4 of 4
Having a problem where shutdown -t 0 now does not shutdown, but ultimately causes an application to run. I suspect there's something bogus in one of the myriad of rc.d ...
- 11-04-2009 #1Just Joined!
- Join Date
- Feb 2009
- Posts
- 6
How do I debug a shutdown problem?
Having a problem where shutdown -t 0 now does not shutdown, but ultimately causes an application to run. I suspect there's something bogus in one of the myriad of rc.d shutdown scripts. Isn't there SOME way to turn on some logging so that I can see how far it is getting through the scripts? Seems kinda nuts there is no way to track shutdown progress...
--
Zinc
- 11-06-2009 #2
Try.....
You don't need '-t 0'Code:shutdown -h now or shutdown -r now
- 11-06-2009 #3Just Joined!
- Join Date
- Feb 2009
- Posts
- 6
I KNOW I don't need '-t 0' the point is, none of the above, including either of your suggestions actually shut down. What they do is startup an application program instead. What I need to know is WHY, and what shutdown script is causing it if it is in fact a bogus shutdown script, as I suspect it is. But I don't know how to determine how far it gets through the shutdown scripts before it stops shutting down. What's needed is some kind of LOGGING that can be turned on to indicate what shutdown script it is about to run or has just run. I suppose I could edit all the shutdown scripts to add logging info, but silly me, I thought there might actually be some useful logging or debug technique for shutdown scripts in general that I could enable somehow...
- 11-08-2009 #4
Look in /etc/rc.d/rc6.d and make sure all scripts are set to kill/stop.


Reply With Quote