Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Just a thought....' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Just a thought....
Authored by: noblee on Mar 04, '03 11:32:42PM

No, the cron tasks will not help here. The errors they are finding are pretty naughty errors in the CONTENT of the files. the cron tasks are mostly dealing with daemons; the cron tasks do not affect the basic file structure. If you are curious, check out:

and the files they direct you to.

That being said, it is never a bad idea to run these scripts.

The concern I have is that I just checked--not a single file error on my PowerBook G4 that has been running now for a little over a year. I am also a pretty hard user on my poor box.

What did these users do that caused this? On my old Linux box, this was not too uncommon, but I was very impressed with OS X for having no file errors on this box until I heard about their stories.

I can see how force quitting could cause this, but I force quit Office apps daily and I kill Fire every few days and Safari once a week. And yet, I have no such corruptions. I would like to see what they all do similarly.

Oh, and I am really not at all sure that this is an OS X issue. I blame it on a cludgy app or apps, or at least I will blame it on non-Apple software until someone shows me an Apple link. Generally, Apple software is better than non-Apple software (even if Apple software is sometimes horribly broken itself!)

[ Reply to This | # ]