Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #62197 > unrolled thread

High Heat

Back to article view | Back to comp.sys.mac.system

Contents

  High Heat gtr <xxx@yyy.zzz> - 2014-07-13 21:15 -0700
    Re: High Heat gtr <xxx@yyy.zzz> - 2014-07-13 21:38 -0700
      Re: High Heat gtr <xxx@yyy.zzz> - 2014-07-13 22:02 -0700
      Re: High Heat David Fritzinger <dfritzin@nospam.mac.com> - 2014-07-14 15:14 -0400
    Re: High Heat Your Name <YourName@YourISP.com> - 2014-07-14 19:13 +1200
      Re: High Heat gtr <xxx@yyy.zzz> - 2014-07-14 10:16 -0700
    Re: High Heat Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-07-14 07:12 -0400
    Re: High Heat Jolly Roger <jollyroger@pobox.com> - 2014-07-14 11:29 +0000
      Re: High Heat gtr <xxx@yyy.zzz> - 2014-07-14 10:11 -0700
        Re: High Heat Jolly Roger <jollyroger@pobox.com> - 2014-07-14 20:18 +0000
          Re: High Heat dorayme <do_ray_me@bigpond.com> - 2014-07-15 08:01 +1000
            Re: High Heat Jolly Roger <jollyroger@pobox.com> - 2014-07-14 22:23 +0000
              Re: High Heat Tim Streater <timstreater@greenbee.net> - 2014-07-14 23:27 +0100
                Re: High Heat Jolly Roger <jollyroger@pobox.com> - 2014-07-14 22:35 +0000
                  Re: High Heat gtr <xxx@yyy.zzz> - 2014-07-14 16:22 -0700
                    Re: High Heat Jolly Roger <jollyroger@pobox.com> - 2014-07-14 23:50 +0000
              Re: High Heat dorayme <do_ray_me@bigpond.com> - 2014-07-15 09:47 +1000
                Re: High Heat Jolly Roger <jollyroger@pobox.com> - 2014-07-15 00:02 +0000
                  Re: High Heat dorayme <do_ray_me@bigpond.com> - 2014-07-15 10:31 +1000
                    Re: High Heat Jolly Roger <jollyroger@pobox.com> - 2014-07-15 01:02 +0000
                      Re: High Heat dorayme <do_ray_me@bigpond.com> - 2014-07-18 17:39 +1000
                        Re: High Heat Jolly Roger <jollyroger@pobox.com> - 2014-07-18 13:26 +0000
                          Re: High Heat dorayme <do_ray_me@bigpond.com> - 2014-07-19 10:02 +1000
                        Re: High Heat Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-07-20 05:44 +0000
                          Re: High Heat Jolly Roger <jollyroger@pobox.com> - 2014-07-20 14:04 +0000
                            Re: High Heat dorayme <do_ray_me@bigpond.com> - 2014-07-21 10:54 +1000
                              Re: High Heat Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-07-22 01:15 +0000
                                Re: High Heat Jolly Roger <jollyroger@pobox.com> - 2014-07-22 14:52 +0000
                    Re: High Heat George Kerby <ghost_topper@hotmail.com> - 2014-07-15 08:27 -0500
          Re: High Heat gtr <xxx@yyy.zzz> - 2014-07-14 16:21 -0700
            Re: High Heat Jolly Roger <jollyroger@pobox.com> - 2014-07-14 23:50 +0000
              Re: High Heat gtr <xxx@yyy.zzz> - 2014-07-14 21:08 -0700
                Re: High Heat Jolly Roger <jollyroger@pobox.com> - 2014-07-15 05:23 +0000
        Re: High Heat George Kerby <ghost_topper@hotmail.com> - 2014-07-15 08:23 -0500
    Re: High Heat billy@MIX.COM - 2014-07-14 15:06 +0000
      Re: High Heat gtr <xxx@yyy.zzz> - 2014-07-14 10:14 -0700
        Re: High Heat billy@MIX.COM - 2014-07-14 17:29 +0000
          Re: High Heat gtr <xxx@yyy.zzz> - 2014-07-14 11:59 -0700
            Re: High Heat billy@MIX.COM - 2014-07-14 21:54 +0000
              Re: High Heat gtr <xxx@yyy.zzz> - 2014-07-14 16:18 -0700
    Re: High Heat gtr <xxx@yyy.zzz> - 2014-07-14 10:18 -0700

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

#62302

In article <c2jctoFcrrvU4@mid.individual.net>,
 Jolly Roger <jollyroger@pobox.com> wrote:

> On 2014-07-15, dorayme <do_ray_me@bigpond.com> wrote:
> >
> > Sure, sometimes you are as thick as a brick. Look again at the thread 
> > and see what you said and gtr's reasonable objection.
> 
> Reasonable? That's debatable. I asked if it had occurred to him to check
> the console and system logs. It's a legitimate question.

You did not *just* do this, you simply cannot see the point. Does not 
mean you are a very bad person, you are just blind to some ordinary 
human social sensitivities. 

Relax, you can't help being you just as Jack Nicholson in As Good as 
it Gets, could not help being himself no matter that Helen Hunt wanted 
him to stop being this for a while.

> Do you have anything of substance to add to this
> conversation, or are you just hell bent on slinging dirt my way in some
> misguided attempt to serve "justice" for gtr?

Nothing to add, and yes, I admit I was a little bent on emphasising an 
injustice. Such small attempts, in the great scheme of things count. 
St Peter, at The Gates will ask me, "And what, dorayme, did you do 
about it?" and I will be able to remind him I did something at least. 

Is this ok? Do you have a problem with it?

-- 
dorayme

[toc] | [prev] | [next] | [standalone]

#62303

On 2014-07-18, dorayme <do_ray_me@bigpond.com> wrote:
> In article <c2jctoFcrrvU4@mid.individual.net>,
>  Jolly Roger <jollyroger@pobox.com> wrote:
>
>> On 2014-07-15, dorayme <do_ray_me@bigpond.com> wrote:
>> >
>> > Sure, sometimes you are as thick as a brick. Look again at the thread 
>> > and see what you said and gtr's reasonable objection.
>> 
>> Reasonable? That's debatable. I asked if it had occurred to him to check
>> the console and system logs. It's a legitimate question.
>
> You did not *just* do this, you simply cannot see the point. Does not 
> mean you are a very bad person, you are just blind to some ordinary 
> human social sensitivities. 
>
> Relax, you can't help being you just as Jack Nicholson in As Good as 
> it Gets, could not help being himself no matter that Helen Hunt wanted 
> him to stop being this for a while.

Your insinuation that I meant to insult, when I meant no such thing, is
both presumptuous and rude. I can only hope you find yourself on the
other end of that stick so that you can appreciate how much of a jerk
you are and change your behavior - not for you, but for others who have
the misfortune of interacting with you.

>> Do you have anything of substance to add to this
>> conversation, or are you just hell bent on slinging dirt my way in some
>> misguided attempt to serve "justice" for gtr?
>
> Nothing to add

As expected. You add very little actual substance to these news groups
at all; most of the time you are trolling or making silly wise cracks
about inconsequential things. You are a complete waste of bandwidth and
time. So I'm done with you completely. Into the kill file you go. No
more wasting my time with your petty arguments. Bye now - see you never.
*plonk*

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#62304

In article <c2slk2FbsojU1@mid.individual.net>,
 Jolly Roger <jollyroger@pobox.com> wrote:

> On 2014-07-18, dorayme <do_ray_me@bigpond.com> wrote:
> > In article <c2jctoFcrrvU4@mid.individual.net>,
> >  Jolly Roger <jollyroger@pobox.com> wrote:
...

> >> Reasonable? That's debatable. I asked if it had occurred to him to check
> >> the console and system logs. It's a legitimate question.
> >
> > You did not *just* do this...
> >
> 
> Your insinuation that I meant to insult

It was the very opposite of this. My point was that you were 
predictably blind to being insulting.

-- 
dorayme

[toc] | [prev] | [next] | [standalone]

#62324

Okay, so one time? In band camp? dorayme <do_ray_me@bigpond.com> was all, like: 
 --> 	 Fri, 18 Jul 2014 17:39:57 +1000 <do_ray_me-0C31D7.17395718072014@aioe.org>
> In article <c2jctoFcrrvU4@mid.individual.net>,
>  Jolly Roger <jollyroger@pobox.com> wrote:

>> On 2014-07-15, dorayme <do_ray_me@bigpond.com> wrote:
>> >
>> > Sure, sometimes you are as thick as a brick. Look again at the thread 
>> > and see what you said and gtr's reasonable objection.
>> 
>> Reasonable? That's debatable. I asked if it had occurred to him to check
>> the console and system logs. It's a legitimate question.

> You did not *just* do this, you simply cannot see the point. Does not 
> mean you are a very bad person, you are just blind to some ordinary 
> human social sensitivities. 

It would be nice if one of the dozens of times you've killfiled JR it
would stick. I know I get tired of your blathering stupidity at him and
making shit up that isn't there, so I imagine he gets tired of it far
sooner.


-- 
"The true measure of a man is how he treats someone who can do him
absolutely no good." ~Samuel Johnson

[toc] | [prev] | [next] | [standalone]

#62327

On 2014-07-20, Lewis <g.kreme@gmail.com.dontsendmecopies> wrote:
> Okay, so one time? In band camp? dorayme <do_ray_me@bigpond.com> was all, like: 
>  --> 	 Fri, 18 Jul 2014 17:39:57 +1000 <do_ray_me-0C31D7.17395718072014@aioe.org>
>> In article <c2jctoFcrrvU4@mid.individual.net>,
>>  Jolly Roger <jollyroger@pobox.com> wrote:
>
>>> On 2014-07-15, dorayme <do_ray_me@bigpond.com> wrote:
>>> >
>>> > Sure, sometimes you are as thick as a brick. Look again at the thread 
>>> > and see what you said and gtr's reasonable objection.
>>> 
>>> Reasonable? That's debatable. I asked if it had occurred to him to check
>>> the console and system logs. It's a legitimate question.
>
>> You did not *just* do this, you simply cannot see the point. Does not 
>> mean you are a very bad person, you are just blind to some ordinary 
>> human social sensitivities. 
>
> It would be nice if one of the dozens of times you've killfiled JR it
> would stick. I know I get tired of your blathering stupidity at him and
> making shit up that isn't there, so I imagine he gets tired of it far
> sooner.

She can holler until she's blue in the face now and I won't see it. : )
Good riddance.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#62328

In article <c320k7Ff217U1@mid.individual.net>,
 Jolly Roger <jollyroger@pobox.com> wrote:

> On 2014-07-20, Lewis <g.kreme@gmail.com.dontsendmecopies> wrote:
> > Okay, so one time? In band camp? dorayme <do_ray_me@bigpond.com> was all, 
> > like: 
> >  --> 	 Fri, 18 Jul 2014 17:39:57 +1000 
> >  <do_ray_me-0C31D7.17395718072014@aioe.org>
> >> In article <c2jctoFcrrvU4@mid.individual.net>,
> >>  Jolly Roger <jollyroger@pobox.com> wrote:
> >
> >>> On 2014-07-15, dorayme <do_ray_me@bigpond.com> wrote:
> >>> >
> >>> > Sure, sometimes you are as thick as a brick. Look again at the thread 
> >>> > and see what you said and gtr's reasonable objection.
> >>> 
> >>> Reasonable? That's debatable. I asked if it had occurred to him to check
> >>> the console and system logs. It's a legitimate question.
> >
> >> You did not *just* do this, you simply cannot see the point. Does not 
> >> mean you are a very bad person, you are just blind to some ordinary 
> >> human social sensitivities. 
> >
> > It would be nice if one of the dozens of times you've killfiled JR it
> > would stick. I know I get tired of your blathering stupidity at him and
> > making shit up that isn't there, so I imagine he gets tired of it far
> > sooner.
>


About k'fing, unlike you and JR, I do not carry the threat around like 
a wild west cowboy with a gun. I have not kf'd JR *dozens of time* 
(but perhaps you are meaning something else and have failed 
punctuation 101) 

About the recent exchanges, JR could not stand the heat in the 
kitchen. It must have been difficult for the poor man. Here was a man 
who could not see the irritating thing he had written to gtr that 
started the exchange with me off. He tried this and that and talked 
about his intentions and not once could see the point. 

In the end, what could the poor schmuck do? Here is this wonderful 
creature from a far away planet come to earth and verbally chiding him 
and he cannot for the life of him see the real issue. He just sees me 
attacking him. He even does not see that the reason it continued is 
that he kept replying! 

> She can holler until she's blue in the face now and I won't see it. : )
> Good riddance.

You see everything, including these words, you simpleton crook. I have 
seen holier than thou and you fit the bill very nicely thank you very 
much. And, btw, my face cannot go blue because I have no face, I am 
not like that... but perhaps you are sophisticated enough to have 
meant it metaphorically (it is hard for me to make a concession like 
this, I think of you as a literalistic autistic who has read a third 
rate handbook somewhere about how to behave in some situations like a 
normal sensitive human). 

Lewis, do me a favour, go jump in a lake, you have always irritated 
the hell out of me. <g>

-- 
dorayme

[toc] | [prev] | [next] | [standalone]

#62351

Okay, so one time? In band camp? dorayme <do_ray_me@bigpond.com> was all, like: 
 --> 	 Mon, 21 Jul 2014 10:54:30 +1000 <do_ray_me-D86B40.10542921072014@aioe.org>
> In article <c320k7Ff217U1@mid.individual.net>,
>  Jolly Roger <jollyroger@pobox.com> wrote:

>> On 2014-07-20, Lewis <g.kreme@gmail.com.dontsendmecopies> wrote:
>> > Okay, so one time? In band camp? dorayme <do_ray_me@bigpond.com> was all, 
>> > like: 
>> >  --> 	 Fri, 18 Jul 2014 17:39:57 +1000 
>> >  <do_ray_me-0C31D7.17395718072014@aioe.org>
>> >> In article <c2jctoFcrrvU4@mid.individual.net>,
>> >>  Jolly Roger <jollyroger@pobox.com> wrote:
>> >
>> >>> On 2014-07-15, dorayme <do_ray_me@bigpond.com> wrote:
>> >>> >
>> >>> > Sure, sometimes you are as thick as a brick. Look again at the thread 
>> >>> > and see what you said and gtr's reasonable objection.
>> >>> 
>> >>> Reasonable? That's debatable. I asked if it had occurred to him to check
>> >>> the console and system logs. It's a legitimate question.
>> >
>> >> You did not *just* do this, you simply cannot see the point. Does not 
>> >> mean you are a very bad person, you are just blind to some ordinary 
>> >> human social sensitivities. 
>> >
>> > It would be nice if one of the dozens of times you've killfiled JR it
>> > would stick. I know I get tired of your blathering stupidity at him and
>> > making shit up that isn't there, so I imagine he gets tired of it far
>> > sooner.
>>


> About k'fing, unlike you and JR, I do not carry the threat around like 
> a wild west cowboy with a gun. I have not kf'd JR *dozens of time* 

It certainly seems that you have said so many times. Perhaps not dozens,
but certainly many. And yet you keep responding to him. You have a
definite bug up your ass about it too, because your responses to him are
*absurdly* abusive and make you look like a fool.

> Here was a man who could not see the irritating thing he had written
> to gtr

Which only you took as irritating, BTW. No one else did, because no one
else is fucking insanse when it comes to JR's posts.

> that started the exchange with me off. He tried this and that and
> talked about his intentions and not once could see the point. 

Maybe if you took off your hat?

> In the end, what could the poor schmuck do? Here is this wonderful 
> creature from a far away planet come to earth and verbally chiding him 

WTF??

> and he cannot for the life of him see the real issue.

That's because THERE WAS NO ISSUE. YOU MADE IT UP.

> He just sees me attacking him.

Because you were attacking him. Duh.

> He even does not see that the reason it continued is that he kept
> replying! 

Oh, right, you didn't keep attacking, it was all him. You really are a
piece of work.

> And, btw, my face cannot go blue because I have no face, I am not like
> that...

Are you on medication? Have you skipped some doses, because this is
fucking insane. It is so completely fucking insane that I am sorely
tempted to add it to my signature file.

...ponder...

Yeah, I think I will add it, and I will also add you to the bozo filter
so that I will nearly never have to read your inane drivel.

> Lewis, do me a favour, go jump in a lake, you have always irritated 
> the hell out of me. <g>

Don't fucking care, I am not completely unbalanced and delusional, so
there's that.

-- 
And, btw, my face cannot go blue because I have no face, I am not like that... 
 --Dorayme, in a fit of nonsensical drivel

[toc] | [prev] | [next] | [standalone]

#62363

On 2014-07-22, Lewis <g.kreme@gmail.com.dontsendmecopies> wrote:
>
> Are you on medication? Have you skipped some doses, because this is
> fucking insane. It is so completely fucking insane that I am sorely
> tempted to add it to my signature file.

Probably going senile.

> ...ponder...
>
> Yeah, I think I will add it, and I will also add you to the bozo filter
> so that I will nearly never have to read your inane drivel.

I can report it's quite nice here with her bullshit filtered out. : )

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#62257

On 7/14/14 7:31 PM, in article do_ray_me-7068D8.10310515072014@aioe.org,
"dorayme" <do_ray_me@bigpond.com> wrote:

> In article <c2j9c0FcrrvU3@mid.individual.net>,
>  Jolly Roger <jollyroger@pobox.com> wrote:
> 
>> On 2014-07-14, dorayme <do_ray_me@bigpond.com> wrote:
>>> In article <c2j3jiFbeprU1@mid.individual.net>,
>>>  Jolly Roger <jollyroger@pobox.com> wrote:
>>> 
>>>> On 2014-07-14, dorayme <do_ray_me@bigpond.com> wrote:
>>> 
>>>>> I thought you would not understand gtr's perfectly reasonable remark?
>>>> 
>>>> Is that supposed to be a question? If so, you'll need to rephrase it
>>>> using correct grammar.
>>>  
>>> Neatly avoiding the real point!
>> 
>> If you have a point, you're certainly not making it very clearly, which
>> leads me to wonder just how sincere you are being. If you have something
>> to say to me, why don't you just say it plainly instead of beating
>> around the bush or trying to disguise it as something it's not?
> 
> Sure, sometimes you are as thick as a brick. Look again at the thread
> and see what you said and gtr's reasonable objection. What is hard to
> understand about me saying that I thought you would not understand his
> point?

Boys, BOYS!!!

:)

[toc] | [prev] | [next] | [standalone]

#62240

On 2014-07-14 20:18:43 +0000, Jolly Roger said:

> On 2014-07-14, gtr <xxx@yyy.zzz> wrote:
>> On 2014-07-14 11:29:56 +0000, Jolly Roger said:
>> 
>>> On 2014-07-14, gtr <xxx@yyy.zzz> wrote:
>>>> My mac's been running slow the past couple of days.  Today I got a
>>>> kernal panic, my first.  Two days ago I had an incredible slowdown of
>>>> response.  I'd open a finder window and it would take 30 seconds of
>>>> waiting before it displayed the contents of the folder.
>>> 
>>> Has it occurred to you to examine the system and console logs during
>>> these slowdowns to see what error messages are posted there at the time
>>> of the problem?
>> 
>> "Did I examine" would seem be less insulting. The answer is yes, but I
>> couldn't find anything of note. That said, there are plenty of ways to
>> insult my ability to parse system and console logs.
> 
> Your inference is wrong. It was not an insult.
> 
> You found zero errors in the logs?

I poked around, I found nothing I could use make sense of, but I'm not 
a "systems logs" reader.  It looks like pages of jibberish to me.  I 
snoop as best I can in this file and that, and  sometimes I see 
something like this:

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

	Exception Type:  EXC_CRASH (SIGABRT)
	Exception Codes: 0x0000000000000000, 0x0000000000000000

It makes me feel like I'm going somewhere but it doesn't mean much.

[toc] | [prev] | [next] | [standalone]

#62243

On 2014-07-14, gtr <xxx@yyy.zzz> wrote:
> On 2014-07-14 20:18:43 +0000, Jolly Roger said:
>
>> You found zero errors in the logs?
>
> I poked around, I found nothing I could use make sense of, but I'm not 
> a "systems logs" reader.  It looks like pages of jibberish to me.  I 
> snoop as best I can in this file and that, and  sometimes I see 
> something like this:
>
> Crashed Thread:  0  Dispatch queue: com.apple.main-thread
>
> 	Exception Type:  EXC_CRASH (SIGABRT)
> 	Exception Codes: 0x0000000000000000, 0x0000000000000000
>
> It makes me feel like I'm going somewhere but it doesn't mean much.

That's a crash log, not the system or console log. Like I said, you're
interested in the "system" and "console" logs - you can ignore the
others. You should look specifically for messages with a date/time stamp
that is during the time period when you last noticed the performance
problem. Suspect messages may have words like: error, failure, can't,
and so on - any words indicating an error condition or problem.

So all you need to do is: (a) note the date and time you notice a
performance problem, and how long it lasts, and (b) examine the console
and system logs for any messages with date/time stamps that are within
that range of time. Then you can post them here for further diagnosis.

Just in case you need any of this info:

Viewing Crash, Console, and System Logs

To view logs on your computer, open /Applications/Utilities/Console.

NOTE: You cannot use the Console application to view the system log from
a non-administrative account. Instead, do this:

1. Quit Console.
2. Open /Applications/Utilities/Terminal.
3. In a terminal window, enter the command (replacing "admin" with the
short name of an administrator account): su admin
4. Supply the password to the admin account when prompted.
5. Enter the command: sudo open /Applications/Utilities/Console.app
6. Supply the password to the admin account when prompted.

If you enter these commands correctly, Console will open in
administrator mode, allowing you to view the system log.

The system log will usually give you an indication as to what is causing
startup and low-level issues, where the console log typically shows
issues you experience after you are logged into your user account.

Feel free to post *relevant portions* (only entries that are time
stamped around the time of the occurrence) of the logs here if you need
help understanding them. We'll be glad to take a look and tell you what
we see.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#62249

On 2014-07-14 23:50:07 +0000, Jolly Roger said:

> On 2014-07-14, gtr <xxx@yyy.zzz> wrote:
>> On 2014-07-14 20:18:43 +0000, Jolly Roger said:
>> 
>>> You found zero errors in the logs?
>> 
>> I poked around, I found nothing I could use make sense of, but I'm not
>> a "systems logs" reader.  It looks like pages of jibberish to me.  I
>> snoop as best I can in this file and that, and  sometimes I see
>> something like this:
>> 
>> Crashed Thread:  0  Dispatch queue: com.apple.main-thread
>> 
>> 	Exception Type:  EXC_CRASH (SIGABRT)
>> 	Exception Codes: 0x0000000000000000, 0x0000000000000000
>> 
>> It makes me feel like I'm going somewhere but it doesn't mean much.
> 
> That's a crash log, not the system or console log. Like I said, you're
> interested in the "system" and "console" logs - you can ignore the
> others. You should look specifically for messages with a date/time stamp
> that is during the time period when you last noticed the performance
> problem. Suspect messages may have words like: error, failure, can't,
> and so on - any words indicating an error condition or problem.
> 
> So all you need to do is: (a) note the date and time you notice a
> performance problem, and how long it lasts, and (b) examine the console
> and system logs for any messages with date/time stamps that are within
> that range of time. Then you can post them here for further diagnosis.
> 
> Just in case you need any of this info:
> 
> Viewing Crash, Console, and System Logs
> 
> To view logs on your computer, open /Applications/Utilities/Console.
> 
> NOTE: You cannot use the Console application to view the system log from
> a non-administrative account. Instead, do this:
> 
> 1. Quit Console.
> 2. Open /Applications/Utilities/Terminal.
> 3. In a terminal window, enter the command (replacing "admin" with the
> short name of an administrator account): su admin
> 4. Supply the password to the admin account when prompted.
> 5. Enter the command: sudo open /Applications/Utilities/Console.app
> 6. Supply the password to the admin account when prompted.
> 
> If you enter these commands correctly, Console will open in
> administrator mode, allowing you to view the system log.
> 
> The system log will usually give you an indication as to what is causing
> startup and low-level issues, where the console log typically shows
> issues you experience after you are logged into your user account.
> 
> Feel free to post *relevant portions* (only entries that are time
> stamped around the time of the occurrence) of the logs here if you need
> help understanding them. We'll be glad to take a look and tell you what
> we see.

Excellent!  Duly stashed for future analysis.  Many thanks.

[toc] | [prev] | [next] | [standalone]

#62251

On 2014-07-15, gtr <xxx@yyy.zzz> wrote:
>
> Excellent!  Duly stashed for future analysis.  Many thanks.

No prob.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#62256

On 7/14/14 12:11 PM, in article 2014071410115775135-xxx@yyyzzz, "gtr"
<xxx@yyy.zzz> wrote:

> On 2014-07-14 11:29:56 +0000, Jolly Roger said:
> 
>> On 2014-07-14, gtr <xxx@yyy.zzz> wrote:
>>> My mac's been running slow the past couple of days.  Today I got a
>>> kernal panic, my first.  Two days ago I had an incredible slowdown of
>>> response.  I'd open a finder window and it would take 30 seconds of
>>> waiting before it displayed the contents of the folder.
>> 
>> Has it occurred to you to examine the system and console logs during
>> these slowdowns to see what error messages are posted there at the time
>> of the problem?
> 
> "Did I examine" would seem be less insulting. The answer is yes, but I
> couldn't find anything of note. That said, there are plenty of ways to
> insult my ability to parse system and console logs.
> 

Down Boy!!!

Seems to me that JR wasn't trying to 'insult', rather to help your
situation.

That time of the month? Wrong side of the bed? Someone pee in your potatoes?

Jeeze..

[toc] | [prev] | [next] | [standalone]

#62206

gtr <xxx@yyy.zzz> writes:

> I'd open a finder window and it would take 30 seconds of 
> waiting before it displayed the contents of the folder.

Mavericks rendering of icons can at times be incredibly slow.
I don't know why, but I do know it's not temperature related.

My hard disk (750GB 5400rpm HGST) is typically 83F, the CPU
cores are 118~120F, graphics processor 126F, etc.

> I turned on the element in iStats menus so I can see my
> temperature.  It's 115.  What should it be.

The best way to know is to have observed it when the computer
was running ok.  The temperatures I posted above have remained
the same since the computer (mid-2012 MacBook Pro) was new.

Billy Y..
-- 
        sub     #'9+1   ,r0             ; convert ascii byte
	add     #9.+1   ,r0             ; to an integer
	bcc     20$                     ; not a number

[toc] | [prev] | [next] | [standalone]

#62212

On 2014-07-14 15:06:06 +0000, billy@MIX.COM said:

> gtr <xxx@yyy.zzz> writes:
> 
>> I'd open a finder window and it would take 30 seconds of
>> waiting before it displayed the contents of the folder.
> 
> Mavericks rendering of icons can at times be incredibly slow.
> I don't know why, but I do know it's not temperature related.
> 
> My hard disk (750GB 5400rpm HGST) is typically 83F, the CPU
> cores are 118~120F, graphics processor 126F, etc.
> 
>> I turned on the element in iStats menus so I can see my
>> temperature.  It's 115.  What should it be.
> 
> The best way to know is to have observed it when the computer
> was running ok.  The temperatures I posted above have remained
> the same since the computer (mid-2012 MacBook Pro) was new.

The temperature given above was for the "CPU heatsink" and is Farenheit.

This morning it was 80-something, and while I drank coffee in the next 
room it has migrated to 108, and is cool to the touch, unlike yesterday.

[toc] | [prev] | [next] | [standalone]

#62215

gtr <xxx@yyy.zzz> writes:

> The temperature given above was for the "CPU heatsink" and is Farenheit.
> 
> This morning it was 80-something, and while I drank coffee in the next 
> room it has migrated to 108, and is cool to the touch, unlike yesterday.

The next time the temperature goes up, use Activity Monitor to see what's
loading (and thus heating up) the CPU.

Billy Y..
-- 
        sub     #'9+1   ,r0             ; convert ascii byte
	add     #9.+1   ,r0             ; to an integer
	bcc     20$                     ; not a number

[toc] | [prev] | [next] | [standalone]

#62221

On 2014-07-14 17:29:44 +0000, billy@MIX.COM said:

> gtr <xxx@yyy.zzz> writes:
> 
>> The temperature given above was for the "CPU heatsink" and is Farenheit.
>> 
>> This morning it was 80-something, and while I drank coffee in the next
>> room it has migrated to 108, and is cool to the touch, unlike yesterday.
> 
> The next time the temperature goes up, use Activity Monitor to see what's
> loading (and thus heating up) the CPU.

It's tough to know when "going up" occurs.  All I'm doing is typing 
emails and usenet stuff and it's at 138F.

The two days that were conspicuous problems, as indicated upstream, I 
was ripping and burning DVD's all day.  It was a warm day.  But I've 
ripped/burned DVD's on warm days before and the thing didn't get 
buggy-eyed and faint on me before.

Regarding my reference to the graph produced by TechTool:

	http://grab.by/yxog

If found an exchange at MicroMat from a company tech that says he 
believes that the element ("temperature changes (190)") in the display 
is obsolute. That's handy. Furthermore, any other discussion of 
elements is to be taken up with the hard-drive manufacturer.  I'm not 
sure why I should discuss "CPU heatsink" readings with the hard-drive 
manufacturer.

[toc] | [prev] | [next] | [standalone]

#62231

gtr <xxx@yyy.zzz> writes:

> If found an exchange at MicroMat from a company tech that says he 
> believes that the element ("temperature changes (190)") in the display 
> is obsolute. That's handy.

Here's some interesting reading about the effect of heat on CPUs -

http://web.archive.org/web/20060316103850/www.sonnettech.com/support/faqs/cpu_faq.html

And here's what I'm using to look at operating parameters -

http://www.bresink.com/osx/HardwareMonitor.html

And a free subset of the above -

http://www.bresink.com/osx/TemperatureMonitor.html

Billy Y..
-- 
        sub     #'9+1   ,r0             ; convert ascii byte
	add     #9.+1   ,r0             ; to an integer
	bcc     20$                     ; not a number

[toc] | [prev] | [next] | [standalone]

#62239

On 2014-07-14 21:54:37 +0000, billy@MIX.COM said:

> And here's what I'm using to look at operating parameters -

Cool, thanks.

[toc] | [prev] | [next] | [standalone]

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

Back to top | Article view | comp.sys.mac.system

csiph-web