![]() If I'm forced to reinstall Leopard from scratch every two weeks AND zero the drive each time, that's not what I call stable.Īs for permission repair, an Apple Genius told me that since updates can change permissions on files, in order to improve stability or others, it is advisable to use Disk Utility from inside OS X, not the Install Disc. The rationale to it is it would have taken more than a night to zero a 160GB drive, and since I'm the only user of this machine, privacy for previous data is not in the point here. This computer was installed on a fully formatted hard drive like, 2 weeks ago, but the drive was not zeroed, just formatted. Incidentaly, I wasn't running any Trash-related task at this time when I do and I know that deleted data is not very sensitive, I just empty it, without "securely" emptying it. In fact, the CPU % use was hovering around 15% when Finder (sort of) crashed, most of which was due to Safari, which is very sensitive to script usage. I do run a good bit of applications at the same time (When Finder refused to cleanly get killed: Safari, Skype, NeoOffice, iCal, Console, iTunes, and one Finder window), but always wait when one needs power. ![]() There's a capability in Finder to connect to WebDAV servers, so I'm using it. ![]() Using the computer the way it's intended to. It's hard to point what I may be doing wrong I'm just Just moderately, because OS X is pretty different from Ubuntu, and used the sudo killall LocumĪs far as WebDAV goes, the capability seems built into OS X (as well as Ubuntu) since a long time. I am, indeed, moderately comfortable with command line. (I don't know a lot about WebDAV, so I'm not sure if what you're talking about involves any third-party software or is using pure Mac OS X functionality.) If the problem comes back, let us know in more detail what it is that you're doing that seems to be causing the problem. Can't hurt to repair permissions as well. Reboot from your Mac OS X install disk and switch to Disk Utility as soon as the installer pops up. If Activity Monitor isn't letting you quit them, get the process ID from Activity Monitor and then try typing "kill 1234" (replacing 1234 with the correct process ID) in the Terminal.Īll that, of course, just solves the current issue, but it sounds like you've got other problems. The kill command will stop a given process. 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. 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". 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |