The kill command will stop a given process.
#RELAUNCH FINDER MAC#
is that correct? If so, you can open the Terminal app on your Mac (found in /Applications/Utilities/) to access the Unix command line.
If you're comfortable in Ubuntu, I assume that means you're at least moderately comfortable with the Unix command line. Ultimately, I think zeroing the drive and reinstalling will be called for, and should fix all of these problems. My current "uptime" is over 16 days, my wife's over 35, so I think Leopard is pretty stable). Keep in mind that, even if your file system gets a clean bill of health from Disk Utility, file damage could remain and cause problems such as the ones you are experiencing (hanging processes, instability, etc.
#RELAUNCH FINDER INSTALL#
The first thing you should do is at least verify the disk in Disk Utility, and perhaps boot to the Leopard install disk to make repairs (if indicated). Unless you have "zeroed" the drive personally, and reinstalled, I wouldn't look beyond this possibility for now. Off the top of my head, I would guess disk error. The fact that you have multiple instances of locum running isn't terribly out of bounds, but the fact that the process hangs and/or cannot be quit is.
I don't know what other functions are performed by locum. I do know that locum is invoked when securely deleting files, so there is some indication here that you either have that option selected in your Finder preferences, or you are using that option from the Finder menu to empty the trash. I'm using MacBook unibody with 10.5.6 and all updates applied, and so far, it seems the most unstable Mac I ever used 😟 So bad for a first ownership. It was a very simple process in Ubuntu, but I don't know what to do in OS X. In the System Monitor, I indeed see 3 Locum operations pertaining to my login name, but I cannot quit or force-quit them.Īs reboot/stop/logout options don't work when Finder has bugged, how can I properly kill the frozen Locum processes, and, even more important, prevent this all-too-common problem from hapenning again? In fact, it seems to have closed, but not relaunched, and indeed, the Console keeps on displaying lines similar to this one:Ġ4/05/09 01:42:10 (0x10e160.Locum) Did not die after sending SIGKILL 1255 seconds ago.Ġ4/05/09 01:42:15 (0x10bf20.Locum) Did not die after sending SIGKILL 1260 seconds ago. I decided to relaunch it using the dialog accessible in altĬmdesc, click on Finder, then click on "Relaunch".
#RELAUNCH FINDER ZIP#
One more time, the Finder failed in its task to cleanly annonce there was an error and properly ask to close the WebDAV connection I was using (), trying to download 30MiB in a few ZIP files.
0 kommentar(er)
