Prev: Graphic Converter users, what is happening here?
Next: MT-NW - signature
From: Mirsky on 28 Apr 2010 22:36
Hi. Lately Safari and Mail are giving me the beach ball and I've had to
force quit. Is there a way for me to figure out why they aren't
responding? I'm not savvy about using Terminal. Thanks
From: dorayme on 28 Apr 2010 22:54
In article <mirsky-5C09ED.19362628042010(a)free.teranews.com>,
Mirsky <mirsky(a)mirsky.com> wrote:

> Hi. Lately Safari and Mail are giving me the beach ball and I've had to
> force quit. Is there a way for me to figure out why they aren't
> responding? I'm not savvy about using Terminal. Thanks

It is truly amazing how folk expect answers to questions like
this without a thought to giving any details. My god, usenet is a
really stupid place! It makes us all stupider than we really are
and attracts stupidity like a black hole sucks particles from
around.

--
dorayme
From: Jolly Roger on 28 Apr 2010 23:27
In article <mirsky-5C09ED.19362628042010(a)free.teranews.com>,
Mirsky <mirsky(a)mirsky.com> wrote:

> Hi. Lately Safari and Mail are giving me the beach ball and I've had to
> force quit. Is there a way for me to figure out why they aren't
> responding? I'm not savvy about using Terminal. Thanks

The way to find out is to examine the system and console logs to see
what, if any, messages related to Mail or Safari are in them.

Viewing Crash, Console, and System Logs

1. Open /Applications/Utilities/Console.

2. From the Console menu bar, select File > View System Log. Typically,
you must be logged into an administrator account to view the system log.

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

a. Open a terminal window.
b. Enter the command (where admin is the short name of an administrator
account): su admin
c. Supply the password to the admin account when prompted.
d. Enter the command: cat /var/log/system.log

If you enter these commands correctly, the system log will be displayed
in the terminal window.

3. From the Console menu bar, select File > View Console 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 only
issues you experience after you are logged into your user account.

If a particular application is crashing, you may find a detailed crash
log in /Library/Logs/CrashReporter/ or
/Users/you/Library/Logs/CrashReporter/. Crash logs typically give a good
indication why a particular application crashed.

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

--
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
 | 
Pages: 1
Prev: Graphic Converter users, what is happening here?
Next: MT-NW - signature