On Mon, 26 Feb 2007, Diane Ross wrote: > On an opposite side...shutting down does clear caches. What you want is the > best of both worlds. You can manually run the nightly cron jobs or you can > reset the time for those chores. I can scrounge up a link for directions if > you are interested.
I know we're getting away from the topic and things like this can be almost religious but clearing caches, like repairing permissions, is something I think is nothing more than a waving of hands - you know, wave your hands over something like a magician does and hope it magically solves the problem. If caches needed to be cleared, why would there even be caches in the first place? The purpose of caches is to avoid repeatedly copying the same data from a "slow" source by keeping a copy in a "faster" source. Of course, there also need to be a mechanism to make sure the cached data is still valid. The biggest reason caches need to be cleared is because the software using it, either by poor design or user option, is not properly refreshing the cached data. > "Problems from insufficient RAM and free hard disk space" is an excellent > source of info. It's not only RAM but free space that needs to be taken into > consideration. I mentioned that earlier but it bears repeating. The amount of free disk space on your STARTUP volume controls the amount of virtual memory your system can use. One source I've read suggests always keeping 5GB free which sounds about right to me. -- Larry Stone [EMAIL PROTECTED] -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
