Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Apple Inc. -- Ignore unavailable to you. Want to Upgrade?

To: NOW who wrote (85301)	9/21/2009 4:16:39 AM
From: Cogito	Read Replies (1) \| Respond to of 213183

>>i am too clueless too even be able to read those files: how would i do that? << NOW - If the system was creating log files that quickly, it will probably just start doing so again. I believe you said this was a fairly new computer, yes? If so, just give Apple Tech Support a call at 800-APL-CARE. They're great. They'll talk you through looking at the log files, or doing whatever else you need. If your computer is less than 90 days old, you're still on free phone support. If it's more than 90 days old, but still less than 3 years, and you've bought AppleCare, you've got free phone support. And if your computer is more than 90 days old but less than one year old and you haven't bought AppleCare, just go ahead and buy it. - Allen

To: NOW who wrote (85301)	9/21/2009 4:04:46 PM
From: Doren	Read Replies (1) \| Respond to of 213183

You should be able to read log files with iText. It may tell you something. The reason I asked if it was multiple files is if it's multiple iterations of the same log file, if you determine which log file you'll know where it comes from and localize the problem. If it's a single log file from the system if you read it it may show some king of repeated behavior. I was able to figure out what was wrong with my DSL by reading the log files from my DSL/Modem/router. In my case I was able to determine the router was incessantly logging in and out. Between me and the service person ATT sent out we determined it wasn't my Mac (of course their useless phone help suggested that first) and the service guy traced it to a legacy chip on my NIC after I explained the incessant logging I'd discovered from the file. 100Gb is absurd. That should not happen. Something is happening over and over and over and in addition it's robbing your processor. Did you partition your drive? If you did and installed a duplicate system on the partition you could boot over to it and determine if it's happening there. If it is not it is a software problem. If it is still happening it is a hardware problem. (This is why I always recommend a partition and extra system.) Everyone says partitioning is not needed, until they can't boot or there is some problem. If it is a system software problem a simple archive and install will probably fix it. If it's a hardware problem, disconnect any peripherals and see if it continues. Last resort. If you have more than one stick of ram remove all but one to see if it continues. Then test each individually.