Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
GGJstudios - you are welcome to check but at least daily scripts require a shut down unless something of recent changed. Tools like Onyx allow as mentioned, the scripts to be ran on the fly.

We can concur on leaving some space available. This is especially true for apps that require "room" to operate and those in particular that create scratch areas or temp areas to work. For my tastes, I prefer to leave 20 percent of the drive available at any given time on my SSD home drive.

We can also concur that permissions is a rather limited area to explore for issues or rather, slowness and issues are less likely to be resolved by a permissions repair but it is still an option that is useful under certain circumstances.

Where caches are concerned, two culprits that seem to further sluggishness are found with font cache and user cache. Where we may disagree is that the trade off for electing to engage them is that for possibly momentary slowness (do to a newly generated cache) the long term effect warrants engaging. Other caches too might prove worthy of from time to time deleting and starting fresh.

OSX does a nice job with its own maint but it can't do everything just the basics and this is wise. Given that so many apps can be challenging, OSX doesn't stand a chance of knowing every nuance and thus remains more generic in its own maint.

As for the rest, we'll just have to agree to disagree on some points and have just slight differences on others.
 
GGJstudios - you are welcome to check but at least daily scripts require a shut down unless something of recent changed. Tools like Onyx allow as mentioned, the scripts to be ran on the fly.

We can concur on leaving some space available. This is especially true for apps that require "room" to operate and those in particular that create scratch areas or temp areas to work. For my tastes, I prefer to leave 20 percent of the drive available at any given time on my SSD home drive.

We can also concur that permissions is a rather limited area to explore for issues or rather, slowness and issues are less likely to be resolved by a permissions repair but it is still an option that is useful under certain circumstances.

Where caches are concerned, two culprits that seem to further sluggishness are found with font cache and user cache. Where we may disagree is that the trade off for electing to engage them is that for possibly momentary slowness (do to a newly generated cache) the long term effect warrants engaging. Other caches too might prove worthy of from time to time deleting and starting fresh.

OSX does a nice job with its own maint but it can't do everything just the basics and this is wise. Given that so many apps can be challenging, OSX doesn't stand a chance of knowing every nuance and thus remains more generic in its own maint.

As for the rest, we'll just have to agree to disagree on some points and have just slight differences on others.

If the computer is asleep, or shut down, when the maintenance scripts are scheduled to run, they will not run and will then run as soon (or shortly after) the computer is awakened or booted up. A full shut down is not necessary to get the scripts to run. I never shut down, and the scripts run when I wake up the computer in the morning.
 
If the computer is asleep, or shut down, when the maintenance scripts are scheduled to run, they will not run and will then run as soon (or shortly after) the computer is awakened or booted up. A full shut down is not necessary to get the scripts to run. I never shut down, and the scripts run when I wake up the computer in the morning.

I stand corrected.
 
If the computer is asleep, or shut down, when the maintenance scripts are scheduled to run, they will not run and will then run as soon (or shortly after) the computer is awakened or booted up. A full shut down is not necessary to get the scripts to run. I never shut down, and the scripts run when I wake up the computer in the morning.
One correction: If the computer is asleep at the scheduled time, the scripts will run when the computer is awake. This is not true in the case of the computer being shut down. The scripts for that scheduled time will not run after boot up, but will instead run at the next scheduled time. If the computer is always shut down at the scheduled maintenance time, the scripts will never run.
GGJstudios - you are welcome to check but at least daily scripts require a shut down unless something of recent changed.
None of the OS X maintenance scripts are triggered by or require a shut down or restart. This has always been the case with OS X maintenance scripts.
 
One correction: If the computer is asleep at the scheduled time, the scripts will run when the computer is awake. This is not true in the case of the computer being shut down. The scripts for that scheduled time will not run after boot up, but will instead run at the next scheduled time. If the computer is always shut down at the scheduled maintenance time, the scripts will never run.

None of the OS X maintenance scripts are triggered by or require a shut down or restart. This has always been the case with OS X maintenance scripts.

As always...thanks for the correction.:D

Some day I'll actually learn some stuff!:eek:
 
Once a week would be too often, though I like my system clean, thus every 17 days.

As for Windows, once I had a very strange problem, which was probably due to a bad HDD, where I had to install Windows 5.0 that often (twice per day), that I could remember the serial number. Ah, those were the days.

Do you see a decline in performance every 17 days?
 
I won't use any of the so called Mac Maintence apps.As I recalled, CleanMyMac is the biggest offender, a borderline virus for the Mac. I mistakenly tried it serval years back, it totally messed up my Mac. Don't do it!!!!

I'm sure you must be thinking of MacKeeper ?
 
I happen to stumble upon this link and candidly, it might be dated but I am unsure. It is worth a read. I am not debating what has been put forth here by others, but certainly welcome any comments about the 'info' below for better or worse.

http://www.thexlab.com/faqs/maintscripts.html

Here is a snippet of the opening -



Running the Mac OS X maintenance scripts

Mac® OS X is a UNIX®-based system, built in part on both BSD® and FreeBSD®. UNIX systems run scheduled maintenance routines — known as maintenance scripts — to clean up a variety of System logs and temporary files. By default, these are executed between 03:15 and 05:30 hours local time, depending on the script.

If your Mac is shut down or in sleep mode during these hours, the maintenance scripts will not run. [1] This results in log files that will grow over time, consuming free space on your Mac OS X startup disk.

If your Mac is shut down or left in sleep mode overnight, the maintenance scripts should be run manually on a regular basis… unless you plan on devoting a large portion of your hard drive to the files cleaned-up by these routines!

This FAQ, derived from our book Troubleshooting Mac OS X, provides:

Procedures for manually running the maintenance scripts.
Determining when the maintenance scripts last ran.
The maintenance performed by the scripts.
How the scripts are launched on a schedule.
 
I happen to stumble upon this link and candidly, it might be dated but I am unsure. It is worth a read. I am not debating what has been put forth here by others, but certainly welcome any comments about the 'info' below for better or worse.

http://www.thexlab.com/faqs/maintscripts.html

Here is a snippet of the opening -



Running the Mac OS X maintenance scripts

Mac® OS X is a UNIX®-based system, built in part on both BSD® and FreeBSD®. UNIX systems run scheduled maintenance routines — known as maintenance scripts — to clean up a variety of System logs and temporary files. By default, these are executed between 03:15 and 05:30 hours local time, depending on the script.

If your Mac is shut down or in sleep mode during these hours, the maintenance scripts will not run. [1] This results in log files that will grow over time, consuming free space on your Mac OS X startup disk.

If your Mac is shut down or left in sleep mode overnight, the maintenance scripts should be run manually on a regular basis… unless you plan on devoting a large portion of your hard drive to the files cleaned-up by these routines!

This FAQ, derived from our book Troubleshooting Mac OS X, provides:

Procedures for manually running the maintenance scripts.
Determining when the maintenance scripts last ran.
The maintenance performed by the scripts.
How the scripts are launched on a schedule.

It is indeed dated. The scripts will now run if the Mac is woken from sleep.
 
MacKeeper belongs to the same league of not needed maintenance software like CleanMyMac.

While its usefulness may be a matter of debate, CleanMyMac most certainly does not deserve to be compared to the malware that is MacKeeper.

Regarding OS X clean installs:

Once a week would be too often, though I like my system clean, thus every 17 days.

That doesn't seem too excessive at all. :rolleyes:

My last clean install was when I got my first iMac in June of 2006 with Tiger. I've upgraded all the way to Mavericks across several Macs since then and it is still running flawlessly, booting to the desktop in about 12 seconds.
 
An issue I had with onyx is every time I run it it would freeze in the second cleaning option and I have too force quite. After this I would the discover I had recovered several gigs of hd space, leading me to believe that their are large logs files being created somewhere.
 
I'm sure you must be thinking of MacKeeper ?

I beg your pardon, I did mean MacKeeper, my apology.
Nonetheless, I would not trust any of the so called Mac "maintenance" junks. I have been using Macs for almost 10 years exclusively, there was never once I need to do what the Windows people have to do and I am a pretty heavy user because of my work.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.