Prev: Keyboard viewer
Next: Quicken 2010 for the Mac
From: Steven Fisher on 12 Apr 2010 02:57
In article <mats-B0D6C3.07290212042010(a)135.115.in-addr.arpa>,
Mats Weber <mats(a)weber.org> wrote:

> I checked, and there is nothing in system.log, nothing in the console,
> and near zero CPU usage.

A stalled (or failing) hard drive not only doesn't consume CPU, but will
actually drive CPU usage, way way down.


Steve
From: Jolly Roger on 12 Apr 2010 11:31
In article <vilain-52988E.01420112042010(a)news.individual.net>,
Michael Vilain <vilain(a)NOspamcop.net> wrote:

> In article <mats-B0D6C3.07290212042010(a)135.115.in-addr.arpa>,
> Mats Weber <mats(a)weber.org> wrote:
>
> > I checked, and there is nothing in system.log, nothing in the console,
> > and near zero CPU usage.
>
> This got posted a while back, possibly by the same guy. Apparently he
> didn't get the memo or figure out the problem. If the hard drive is
> failing, he'll figure it out sooner or later. Even if he says he can't
> find any problems.

He doesn't mention Disk Utility, so I guess he figured that wasn't
needed. *shrug*

He can't seem to figure out how to reply to other posts either.

--
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.

JR
First  |  Prev  | 
Pages: 1 2 3
Prev: Keyboard viewer
Next: Quicken 2010 for the Mac