Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Jolly Roger Newsgroups: comp.sys.mac.system Subject: Re: Beach Ball Blues Date: 27 Jun 2014 01:56:38 GMT Organization: People for the Ethical Treatment of Pirates Lines: 49 Message-ID: References: <1lnquvf.1g6449ef6k1stN%csampson@inetworld.net> <1lnuzri.n5tect11n1pkzN%csampson@inetworld.net> X-Trace: individual.net pw8Fan/DmkIGV9H8hohxcwG37Sc3+dVk5st+rpGugvfVAOy1Ls Cancel-Lock: sha1:Y2BNCpFyTZixzgxu1bCKoOuwCyE= X-Face: _.g>n!a$f3/H3jA]>9pN55*5<`}Tud57>1Y%b|b-Y~()~\t,LZ3e up1/bO{=-) User-Agent: slrn/1.0.1 (Darwin) Xref: csiph.com comp.sys.mac.system:61447 On 2014-06-27, Charles H. Sampson wrote: > Jolly Roger wrote: > >> Well the symptoms you describe are certainly within range of a >> malfunctioning disk drive; but it's best not to jump to conclusions >> without first having a quick look at your system. Unfortunately, SMART >> often doesn't tell you much until after the disk fails. I would first >> look for messages that are posted to the console and system logs at the >> time of the sluggishness. Messages that have a time stamp that is close >> to or during the sluggish event (while the beach ball is on screen, for >> instance) may give you an indication of what is causing the performance >> issue. For instance, you might see messages about IO or disks, >> indicating a failing disk. Or you might see error messages about network >> services or something else entirely. If needed, you can post the >> relevant messages here and we can help you figure out what's going on. > > Thanks for the suggestion. Do you know the names of these log > files? When I did a search for "log" I got 16,212 hits. To view logs on your computer, open /Applications/Utilities/Console. NOTE: You might notice that Console refuses to allow you to view the system log if you are currently logged into a non-administrator Mac OS X user account. If that happens you can 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, the Console application 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 only issues you experience after you are logged into your user account. Again, please post only the *relevant* log messages (those with time stamps during the period of time when the sluggishness is occurring), so that we don't have to wade through hundreds of irrelevant lines. -- 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