Problems shutting down |
December, 28, 2002 6:01 PM |
ed |
I know - real Mac users never shut their machines off. Still, I occasionally need to boot into 9.1 in order to burn CD-Rs (see related thread), and have often encountered this problem. Sometimes, if I choose Shut Down from the Apple menu (or log out first, then press the shutdown button, the blue screen just hangs on forever (with the rotating windmill, or before I upgraded to Jaguar, the lovely beachball). The only choice (that I know of) is to restart with Control-Command-Power, and that does not do good things for the disk (during fsck it finds an orphaned indirect inode). Although this always happened (since 10.0.0), it now appears to be related to the CD-R-light- flashing problem I describe in my other thread. It is possible to shut down the system safely with the Terminal application, by sending the right signal to init (kill -INTR 1 usually does the trick), which drops you into full-screen single user mode, where you can simply give the halt command. However, I would like to do things less drastically. A (prehaps) unrelated problem is when Finder hangs up, and using "reload" (or whatever it is) from the Force Quit dialog makes matters worse by leaving you without a menubar (sometimes the dock seems to work, though). It would be nice if there were a combination of keys that can kill Aqua and put you into full-screen console mode, but I don't have the time or guts to develop it myself. |
. |
RE: Problems shutting down |
January, 20, 2003 10:44 AM |
OSXGuru |
. |
Probably your best bet is to look in the system log (/var/log/system.log) and see whether there is anything interesting there to explain why the shutdown is not proceeding properly. Instead of killing init, another alternative method for shutting down is the following command in the terminal: shutdown -h now This will at least sync the disks, though I don't think it will allow applications to exit gracefully (i.e. save your work and quit applications first). |
. |
RE: Problems shutting down |
December, 28, 2002 11:55 PM |
ed |
. |
Sorry, that should be kill -TERM 1 Also, in the minimal state the system is in after sending TERM to init, you probably shouldn't do anything other than sync, reboot or halt - I tried ^D to put it back into multi-user mode and it went crazy. However, none of this works if you can't start the Terminal app to begin with, as happens when the finder or the loginapp has hung up or crashed. |
|
|